Redirecting to ...

Tuning Rainbows!

Most of the tuning notes apply to Rainbows! as well. Rainbows! is not particularly optimized at the moment and is designed for applications that spend large amounts of the time waiting on network activity. Thus memory usage and memory bandwidth for keeping connections open are often limiting factors as well.

As of October 2009, absolutely ZERO work has been done for performance validation and tuning. Furthermore, Rainbows! is NOT expected to do well on traditional benchmarks. Remember that Rainbows! is only designed for applications that sleep and/or trickle network traffic. In the future, may do well in traditional benchmarks as a side effect, but that will never be the primary goal of the project.

Rainbows! configuration

nginx configuration

If you intend to use nginx as a reverse-proxy in front of Rainbows! to handle Comet applications, make sure you disable proxy response buffering in nginx:

proxy_buffering off;

This can be disabled on a per-backend basis in nginx, so under no circumstances should you disable response buffering to Unicorn backends, only to Rainbows! backends.

Originally generated with the Darkfish Rdoc Generator 2, modified by wrongdoc.

We love to hear from you!
Email patches (with git send-email), pull requests, questions, bug reports, suggestions, etc. to us publically at
No subscription to the mailing list is necessary, just let us know to Cc: you if you're unsubscribed.
To subscribe, email with "subscribe" in the Subject and respond to the automated confirmation message.
Do not waste bandwidth with HTML, HTML mail will not be read.
Quote only parts you're responding to and do not top post.
For sensitive topics, email us privately at