The post itself is a bit too dismissive to my taste but the comments
make for an interesting read:
"Another showstopper is the fact that the Rack binding in Rails 2.3
loads entire file uploads into memory (instead of just storing a
reference to the file). This causes any app that processes uploads to
leak memory like there's no tomorrow"
Uh-oh.
And then later on, Hongli Lai (from Passenger) says: "That's partially
Phusion Passenger's fault. Upgrade to Phusion Passenger 2.2.2 and you
should be fine"
Well, it seems serious enough to warrant a double upgrade, but I am
not sure if the bug applies only if one uses Rack or it basically
applies to all??
> Well, it seems serious enough to warrant a double upgrade, but I am > not sure if the bug applies only if one uses Rack or it basically > applies to all??
> If anyone can shed any light on this...
I upgraded to rails 2.3 I had already upgraded passenger before I deployed my app.
The passenger upgrade went without a hitch. The rails upgrade required a lot of code changes and upgrading a lot of plugins.
If you have gone through the trouble of upgrading rails I'd suggest you upgrade passenger. It only takes a few seconds.
On 26/06/2009, at 9:50 PM, Cyrille <cbonne...@gmail.com> wrote:
I'm a bit out of touch with Rails at the mo…
> Well, it seems serious enough to warrant a double upgrade, but I am > not sure if the bug applies only if one uses Rack or it basically > applies to all??
yeah, and Rails Metail is worth looking at if you want to dodge
ActionController entirely. We are about to use this for some high
volume actions to see if it makes any difference.
nahum.
On Jun 27, 11:36 am, Henry Maddocks <henry.maddo...@gmail.com> wrote:
> On 26/06/2009, at 9:50 PM, Cyrille <cbonne...@gmail.com> wrote:
> I'm a bit out of touch with Rails at the mo…
> > Well, it seems serious enough to warrant a double upgrade, but I am
> > not sure if the bug applies only if one uses Rack or it basically
> > applies to all??
On Fri, Jun 26, 2009 at 9:50 PM, Cyrille<cbonne...@gmail.com> wrote: > And then later on, Hongli Lai (from Passenger) says: "That's partially > Phusion Passenger's fault. Upgrade to Phusion Passenger 2.2.2 and you > should be fine"
> Well, it seems serious enough to warrant a double upgrade, but I am > not sure if the bug applies only if one uses Rack or it basically > applies to all??
From 2.3 on, Rails uses Rack as the glue between Rails and the webserver, so yes you will be using it.
You should upgrade Passenger when you upgrade to 2.3, because 2.3.3 at least contains an updated version of Rack that is not fully compatible with early versions of Passenger.
You should be able to upgrade Passenger while still on 2.2 if you're nervous about upgrading both at the same time, but we tried out latest REE + current Passenger + Rails 2.3.3 on a staging server on thursday and it tested out fine (no errors under load test etc.).