Allrighty, mongrel -B is running and producing the log. Do you have any pointers on how to interpret the log?
on fastthread:
[EMAIL PROTECTED]/home/websites/gomagazine$ gem list fastthread
*** LOCAL GEMS ***
fastthread (0.6.4.1)
Optimized replacement for thread.rb primitives
Op 7-mrt-2007, om 19:38 heeft Zed A. Shaw het volgende geschreven:
On Tue, 6 Mar 2007 21:13:06 +0100 joost baaij <[EMAIL PROTECTED]> wrote:Hmm, reading that I am growing more suspicious. My ram-related woes appeared when Rails 1.2 hit the stage. But I also saw a hefty increase in traffic so was quick to blame it on that.I haven't investigated it yet but you should probably test it out and double check you've got fastthread in there. If you run mongrel_railswith -B you can get a log/mongrel_debug/objects.log file that will helpyou track down the memory problems. Let me know what you find. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/ http://www.awprofessional.com/title/0321483502 -- The Mongrel Book http://mongrel.rubyforge.org/ _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
-- www.gomagazine.nl +31643904460 pobox 51059 nl-1007eb amsterdam
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
