Comments on: What’s the story morning glory? http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/ Ecchi nanowa ikenai to omoimasu Sat, 05 Jul 2008 18:34:48 +0000 http://wordpress.org/?v=2.3.3 By: Hongli http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7993 Hongli Thu, 27 Mar 2008 17:24:27 +0000 http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7993 <blockquote>I assume you fork per request?</blockquote> No, that would be inefficient. We do resource pooling. The exact algorithm is well-documented and will be available to developers once it has been released. Assets such as images and stylesheets (as well as page caching files) do not go through Rails at all, resulting in a huge performance boost. Advanced process management features such as process size limits is beyond the scope of version 1.0, but might be interesting to look at for future versions. <blockquote>Good job. I submitted a suggestion to ruby central that they sponsor a Google Summer of Code to help the project :)</blockquote> Thanks :)

I assume you fork per request?

No, that would be inefficient. We do resource pooling. The exact algorithm is well-documented and will be available to developers once it has been released. Assets such as images and stylesheets (as well as page caching files) do not go through Rails at all, resulting in a huge performance boost. Advanced process management features such as process size limits is beyond the scope of version 1.0, but might be interesting to look at for future versions.

Good job. I submitted a suggestion to ruby central that they sponsor a Google Summer of Code to help the project :)

Thanks :)

]]> By: roger http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7991 roger Thu, 27 Mar 2008 16:33:13 +0000 http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7991 Rock on this is just the type of thing that rails needs to be accepted more, and be far far less painful to deploy. Some random thoughts: I assume you fork per request? Some niceties would be to be able to have a 'timeout' per request. Perhaps another useful one would be the optional ability to limit the size of the process as it is running (and kill it should it grow too large). It would also be nice if apache were trained to return the 'right' headers for assets, as well (i.e. cacheable :forever appropriately). Good job. I submitted a suggestion to ruby central that they sponsor a Google Summer of Code to help the project :) Take care. -R Rock on this is just the type of thing that rails needs to be accepted more, and be far far less painful to deploy.
Some random thoughts: I assume you fork per request? Some niceties would be to be able to have a ‘timeout’ per request.
Perhaps another useful one would be the optional ability to limit the size of the process as it is running (and kill it should it grow too large).
It would also be nice if apache were trained to return the ‘right’ headers for assets, as well (i.e. cacheable :forever appropriately).

Good job. I submitted a suggestion to ruby central that they sponsor a Google Summer of Code to help the project :)
Take care.
-R

]]> By: LisaK http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7985 LisaK Thu, 27 Mar 2008 12:20:44 +0000 http://izumi.plan99.net/blog/index.php/2008/03/26/what%e2%80%99s-the-story-morning-glory/#comment-7985 Fantastic news -- thanks for all of your work! :D Fantastic news — thanks for all of your work! :D

]]>