From: "Francis Cianfrocca" <garbagecat10 / gmail.com>
>
> This is a perfect example of what I've noticed many times: Ruby's
> performance is perfectly fast and acceptable until the working set gets a
> certain (not terribly large) size, then it falls off a cliff. GC perhaps has
> something to do with it, but I suspect that's only a small part of the
> problem.

Can anyone speculate as to what other subsystems or facets of Ruby's
architecture, besides GC, might possibly cause this?


Regards,

Bill