> Rails is not thread-safe, so mongrel locks it. You could implement > these tasks in a custom mongrel handler, or look into ezra's > backgrounddrb plugin. > > http://www.brainspl.at/articles/2006/05/15/backgoundrb-initial-release > > -- > Rick Olson > http://techno-weenie.net >
I realize that mongrel is not thread safe, I was hoping mongrel might spawn a few processes and serve them in the background to emulate what I wanted. I have looked at the backgrounddrb plug-in and will use that for things like statement generation, and very long running tasks. The problem is I am accessing a system that I cannot change (for the time being) and the length of time for the queries are directly proportional to how much data each customer may have. So most queries are fast enough, but some customers have so much data that they bog things down. I would have to make everything a remote call, more work and overhead than I am looking for. On top of that I cannot change the indexes or table structure (we are accessing tables that another program accesses). At some point we will build a new system from scratch to address these issues, but for the time being I am stuck with what I have. Anyone know of a simple win32 web proxy that can deal with multiple mongrel servers? Thanks, Walt -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.7.0/345 - Release Date: 5/22/2006
_______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
