Hi,

In message "Re: Ruby, memory and speed"
    on Fri, 18 Aug 2006 00:16:33 +0900, "Francis Cianfrocca" <garbagecat10 / gmail.com> writes:

|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.

This may be caused by the problem addressed in 1.9:

   Mon Jul 10 19:22:19 2006  Tanaka Akira  <akr / fsij.org>

	* gc.c (gc_sweep): expand heap earlier.
	  reported by MORITA Naoyuki.  [ruby-dev:28960]

							matz.