Comments on: Making Ruby’s garbage collector copy-on-write friendly, part 5 http://izumi.plan99.net/blog/index.php/2007/10/14/making-ruby%e2%80%99s-garbage-collector-copy-on-write-friendly-part-5/ Ecchi nanowa ikenai to omoimasu Sat, 05 Jul 2008 18:36:08 +0000 http://wordpress.org/?v=2.3.3 By: Hongli http://izumi.plan99.net/blog/index.php/2007/10/14/making-ruby%e2%80%99s-garbage-collector-copy-on-write-friendly-part-5/#comment-7464 Hongli Mon, 10 Dec 2007 21:37:46 +0000 http://izumi.plan99.net/blog/index.php/2007/10/14/making-ruby%e2%80%99s-garbage-collector-copy-on-write-friendly-part-5/#comment-7464 Hi Kevin Watt. Good that you show interest. It has already been solved though, please click on the "Optimizing Rails" category and see part 6. Hi Kevin Watt. Good that you show interest. It has already been solved though, please click on the “Optimizing Rails” category and see part 6.

]]> By: Kevin Watt http://izumi.plan99.net/blog/index.php/2007/10/14/making-ruby%e2%80%99s-garbage-collector-copy-on-write-friendly-part-5/#comment-7462 Kevin Watt Mon, 10 Dec 2007 17:35:39 +0000 http://izumi.plan99.net/blog/index.php/2007/10/14/making-ruby%e2%80%99s-garbage-collector-copy-on-write-friendly-part-5/#comment-7462 Since this got mentioned in the slashdot post about ROR recently, I wanted to reply and say that this is a huge deal for me, and I am super-looking forward to a solution. I know ruby allocates memory in "slabs" of incresaing size. For example, the next one after 80mb or so is like 40 megs, which pushes you rmemory to 120Mb and that sucks. Perhaps the one after 30k is 7mb. The real problem, in my mind, is that ruby's garbage collector kills the crap out of copy-on-write... something Eric Hodel+others are working on. At least they were, I hope they're successful soon :) Since this got mentioned in the slashdot post about ROR recently, I wanted to reply and say that this is a huge deal for me, and I am super-looking forward to a solution.

I know ruby allocates memory in “slabs” of incresaing size. For example, the next one after 80mb or so is like 40 megs, which pushes you rmemory to 120Mb and that sucks. Perhaps the one after 30k is 7mb.

The real problem, in my mind, is that ruby’s garbage collector kills the crap out of copy-on-write… something Eric Hodel+others are working on. At least they were, I hope they’re successful soon :)

]]>