On 6/18/06, Jamis Buck <[EMAIL PROTECTED]> wrote:
On Jun 18, 2006, at 4:53 PM, Solomon White wrote:
> Jamis--
>
> Seems to have worked for us, we're back on edge. How far from
> production-ready do you estimate the new routes implementation to
> be? We're about to convert a fairly high-traffic site from its
> current JSP implementation to our rails app, and I need to decide
> whether to freeze before or after new routes...
Well, as far as I know, the only outstanding routing-related ticket
is http://dev.rubyonrails.org/ticket/5320. I haven't had a chance to
look into it yet. So, if the rails trac is any indication, it sounds
like not many people are having issues with the new routes, and we
may be close to production-ready, though I'd like to hear from a lot
more people that are actually using it before I make that declaration
with any confidence.
I've run into some nasty and repeatable memory leakage in recent Rails
revisions. Running on 4450-something, I managed to make the Linux
kernel's OOM-killer shut down the Rails processes.
Rolling back to 4358 fixed it, with no other changes.
I'm trying to find time to narrow down the leak to a specific
revision, but from the changelog, the only major change seems to be
the new routing code.
Anyone feel like looping 'ab' against one of their apps, in production mode?
Here's the command I used:
while true; do /usr/sbin/ab -n 1000 -c 30 http://example.com/
2>/dev/null | grep quest.*mean ; echo -- ; done
I've got two apps that don't go above 21MB of usage during that
process when running on 4358, and die by running out of memory on the
latest edge.
--Wilson.
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
