This post originated from an RSS feed registered with Ruby Buzz
by Michael Neumann.
Original Post: Memory Usage of Wee with Continuations
Feed Title: Mike's Weblog
Feed URL: http://www.ntecs.de/blog-old/index.rss?cat=ruby&count=7
Feed Description: Blogging about Ruby and other interesting stuff.
The whole long night, my laptop was running and stressing a Wee application
to find memory leaks in the current continuation implementation. I started
with 25 stress processes, after 14 hours, there were only 16 of them still
alive. The other 9 processes died for a yet unknown reason (probably a
connection related problem). All in all, the processes created around 7.5
million requests, in 14 hours or 50000 seconds, and memory consumption did
not exceed the magic 20 MB mark. This time I used Ruby from the stable
branch.
This is an average of 150 requests per second or if we don't count the
redirects, which make the half of the requests, this is still an impressive
performance of 75 whole page views per second (on a 1300 MHz Centrino
laptop, running KDE with lot's of open applications). Of course this time,
the web application was a very simple one, it showed only a chain
of dialog boxes.
Previous Topic
