> It's another well-known fact about running on the JVM that we have to
> suck it up and accept there's an initial memory chunk eaten up by every
> JVM process. If one excludes that initial cost, most measurements have
> us using less memory than C Ruby...so for very large apps we end up
> coming out ahead. But for small, short apps, the initial slow startup
> and high memory usage is going to be a battle we fight for a long time.
> 
> - Charlie

If you run multiple threads I assume there isn't an extra memory cost 
for that--is that right?
-- 
Posted via http://www.ruby-forum.com/.