search for: 51059

I had posted a thread couple of weeks ago whereby mongrel just mysteriously stops interacting with my application after an idle period...usually less than 8 hours. http://rubyforge.org/pipermail/mongrel-users/2007-February/002908.html I had hoped this would go away after a few upgrades but to know avail. Interestingly, the process does not die...it still accepts HTTP requests but does not

I''m a bit surprised I can''t find anything about this in the mailing list archives. Basically since Mongrel 1.0.1 I''ve had Mongrels fall asleep without any real cause. A deep sleep, actually more like a coma. The mongrel in question (I''m using a cluster of three) can not be revived. A cluster::stop, then cluster::start is nessesary. A ::restart would not

I see that Brian McCallister did some benchmarks recently, showing Apache, Mongrel, Jetty and TwisteWeb: http://kasparov.skife.org/blog/src/ruby/silly-micro-benchmarks.html Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

...Yes! Apparently people have been able to get RMagick running fine on a busy site, but I am not one of them. Happily running a Mongrel trio again (behind LiteSpeed). The new lighttpd 1.5 architecture looks promising, maybe I''ll switch back. -- www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam

We have a site that is running Mongrel and is down. Below is the Mongrel log file information. The server is a Linux server with 2gb of RAM. EV1 (hosting site) says that since this is a Linux server that the RAM is cached and that there is plenty of free memory available. Can anyone make sense of this error and have some suggestion of options that I may take to correct this issue and get

I have an application which uses send_file to send a ZIP file to the client. This works nicely when it''s run on our development OS-X boxes, using mongrel from script/server, but on our production server, using mongrel behind Apache 2.2. with mod_proxy_balancer, the client gets 1 byte delivered :-( If I use wget -S to the URL in order to see the full headers I see this on

I''ve been getting a bunch of reports about the latest Rails "leaking" memory more than before. Please fill out this survey: 1) Have you noticed an increase in memory usage with the latest Rails 1.2? 2) Have you changed anything else in your application? a) No, really, don''t be a dumbass like the lusers you hate. Go look at your svn logs and really figure out if