Hi, Are there any recommendations as to what is currently the most stable setup is for mongrel & apache? I read somewhere (probably here) that you should avoid using PStore for sessions. Are there any more of such recommendations? Also, what is currently the safest version of mongrel to use in production? Jeroen
I would definitely use rake db:sessions:create (ActiveRecord Store) that way your sessions are all in one central place and all mongrel nodes can access it. (of course assuming you''re using rails :-p) And Apache 2.2.3 (compiled from source with mod_proxy_balancer) and the latest mongrel gem has worked great for me thus far. :: my 2 cents :: cheers, -rjs- On 11/30/06, Jeroen Houben <jeroen at supercool.nl> wrote:> > Hi, > > Are there any recommendations as to what is currently the most stable > setup is for mongrel & apache? I read somewhere (probably here) that you > should avoid using PStore for sessions. Are there any more of such > recommendations? Also, what is currently the safest version of mongrel > to use in production? > > Jeroen > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061130/458210a2/attachment.html
On Thu, 30 Nov 2006 22:07:51 +0100 Jeroen Houben <jeroen at supercool.nl> wrote:> Hi, > > Are there any recommendations as to what is currently the most stable > setup is for mongrel & apache? I read somewhere (probably here) that you > should avoid using PStore for sessions. Are there any more of such > recommendations? Also, what is currently the safest version of mongrel > to use in production?General warning is using any external libraries that require sharing OS level resources (files, sockets, shmem, file locks) should be avoided or very strictly tested and controlled. Additionally, if you *must* use these put them into a separate DRb server and make it the single control point for the resources. Also, try to avoid RMagick processing inside rails. People love their file_column, but RMagick is a fat nasty pig that cripples many sites without warning. The optimal setup is use something like BackgrounDRb or a plain DRb server and use a batch processing method. That''s the main warnings right now. -- 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/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.
> Also, try to avoid RMagick processing inside rails.People love their file_column, but RMagick is a fat nasty pig that cripples many sites without warning. The optimal setup is use something like BackgrounDRb or a plain DRb server and use a batch processing method. I don''t use file_column, but do use RMagick and haven''t had any problems (and its author has been helpful with support). But I also only allow admins to use it. 43Things resizes images on the fly -- not sure if they use rmagick, but with all their users and all those images, it''s gotta bump up the cpu and memory requirements quite a bit. Joe Ruby MUDCRAP-CE "Believe nothing, test everything!" ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited
Zed A. Shaw wrote:> On Thu, 30 Nov 2006 22:07:51 +0100 > Jeroen Houben <jeroen at supercool.nl> wrote: > >> Hi, >> >> Are there any recommendations as to what is currently the most stable >> setup is for mongrel & apache? I read somewhere (probably here) that you >> should avoid using PStore for sessions. Are there any more of such >> recommendations? Also, what is currently the safest version of mongrel >> to use in production? > > General warning is using any external libraries that require sharing OS level resources (files, sockets, shmem, file locks) should be avoided or very strictly tested and controlled. Additionally, if you *must* use these put them into a separate DRb server and make it the single control point for the resources.I use Ruby''s built-in IO functions to fetch some external RSS and do some file caching. Would you consider this a hazard? I had a Rails site that had gone 500 when it couldn''t connect to the external feed. This was due to a lack of error checking on my behalf. The weird thing was that other Rails sites on the same box also stopped responding. I know this is a vague problem description, I''ll try and get to the logs and see if I can spot anything.> Also, try to avoid RMagick processing inside rails. People love their file_column, but RMagick is a fat nasty pig that cripples many sites without warning. The optimal setup is use something like BackgrounDRb or a plain DRb server and use a batch processing method. > > That''s the main warnings right now.Thanks Zed. Jeroen
On Fri, 01 Dec 2006 09:05:50 +0100 Jeroen Houben <jeroen at supercool.nl> wrote:> Zed A. Shaw wrote: > > On Thu, 30 Nov 2006 22:07:51 +0100 > > Jeroen Houben <jeroen at supercool.nl> wrote:> I use Ruby''s built-in IO functions to fetch some external RSS and do > some file caching. Would you consider this a hazard? I had a Rails site > that had gone 500 when it couldn''t connect to the external feed. This > was due to a lack of error checking on my behalf. The weird thing was > that other Rails sites on the same box also stopped responding. I know > this is a vague problem description, I''ll try and get to the logs and > see if I can spot anything.It can be a problem if the source of the RSS is unreliable, like off the network, or if you''re doing DNS queries against a flaky DNS server. Ruby''s interpreter actually stops completely during most DNS queries so if you are using say net/http to connect to a flaky web site you could block the whole show. I''m not sure why all your ruby processes went down, but you should try to replicate it and figure out what is the cause. -- 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/ http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.