Eric Hodel wrote:

> Can you run it under the profiler?

sure - using 'top' (the extent of my profiling knowledge) i can see that 
gem is using
cpu - negligible (0.2%)
ram - 10% (of the virtual memory allocated to the virtual machine?)
virt - 63624 (is this in kB? 63 meg sounds about right for 10%)

So, it doesn't seem to be using excessive amounts of memory, but i don't 
know enough to tell whether lots of swapping is happening.

Thanks for the help guys btw :)
-- 
Posted via http://www.ruby-forum.com/.