Hi, I'm contracting for an Ad Serving company and we were mooting the idea of writing our own lean and mean web server for serving the Ads. We would like to hold all the Ads in memory (each Ad is less than 20K). The next thing is to create a pool of mod_perl-esque processes that will handle the AD requests and also hold persistent connections to the database. I would like to write this mini-server in perl ... but maybe a threaded programming language is better? Does anyone know a good process/threading model for handling the requests and passing them around? Will we see a significant performance improvement in any event? NIge
- Re: Connection Pooling / TP Monitor Jeff Horn
- Re: Connection Pooling / TP Monitor Matt Sergeant
- Re: Connection Pooling / TP Monitor Les Mikesell
- Re: Connection Pooling / TP Monitor Matt Sergeant
- Re: Connection Pooling / TP Monitor Gunther Birznieks
- Re: Connection Pooling / TP Monitor G.W. Haywood
- Re: Connection Pooling / TP Monitor David Hodgkinson
- Re: Connection Pooling / TP Monitor Gunther Birznieks
- Re: Connection Pooling / TP Monitor Leslie Mikesell
- Re: Connection Pooling / TP Monitor Gunther Birznieks
- Re: HTTP Mod_Perl mini-server Nigel Hamilton
- Re: HTTP Mod_Perl mini-server Matt Sergeant
- Re: HTTP Mod_Perl mini-server David Hodgkinson
- Re: HTTP Mod_Perl mini-server Perrin Harkins
- Re: HTTP Mod_Perl mini-server David Hodgkinson
- Re: HTTP Mod_Perl mini-server Perrin Harkins
- Re: HTTP Mod_Perl mini-server Vivek Khera
- Re: HTTP Mod_Perl mini-server Perrin Harkins
- [ NOW OT ] Re: HTTP Mod_Perl mini-server Greg Cope
- Re: HTTP Mod_Perl mini-server Greg Stark
- Re: HTTP Mod_Perl mini-server spam