From: Brent Roman <brent@...>
Date: 2008-12-23T13:27:58+09:00
Subject: [ruby-core:20816] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use


My patches don't mess with any of the pthread stuff.

I'm a pleasantly surprised by your rails benchmark results.
I would have expected this memory savings, but I can't think of why a single
threaded application like Rails (that doesn't use Continuations), would see
the sort of speed up you observed.  I'd expect it to be 2 to 10 percent
slower unless it was doing a lot of context switches.

I did get an off list response from a chinese website that confirms the
rails memory savings, but
they said there was no change in speed.

Does your Rails application use threads or continuations?

Are you comparing ruby built from the same source tarball with the same
compiler options before and after patching?

- brent



hemant-6 wrote:
> 
> Hey Brent,
> 
> Thanks for patches man. I am yet to dig deeper, but I benchmarked
> rails against them:
> 
> Here is the Average request/response for patched version:
> 
> Requests per second:    234.77 [#/sec] (mean)
> Time per request:       42.594 [ms] (mean)
> Time per request:       4.259 [ms] (mean, across all concurrent requests)
> Transfer rate:          108.82 [Kbytes/sec] received
> 
> Memory usage stayed around 30MB
> 
> For Stock Ruby version:
> 
> Requests per second:    138.48 [#/sec] (mean)
> Time per request:       72.214 [ms] (mean)
> Time per request:       7.221 [ms] (mean, across all concurrent requests)
> Transfer rate:          64.21 [Kbytes/sec] received
> 
> 
> Memory usage stayed around 53 MB
> 
> I compiled both ruby versions without "--disable-pthread" and was
> wondering if your patches modify anything there.
> 
> 

-- 
View this message in context: http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p21139498.html
Sent from the ruby-core mailing list archive at Nabble.com.