On Thu, 2007-02-15 at 12:07 -0500, [EMAIL PROTECTED] wrote: > The project I was doing required either heavy threading or asynch IO. It > was basically replaying production application server traffic in real time > so we could run our new database cluster in parallel with our old one for > a couple of weeks before replacing the old one. > > Since it was doing a lot of HTTP requests, I didn't have time to write my > own HTTP library, and I wanted to use an existing lib, I ended up choosing > threads and Python.
I wonder how an asynchronous http library, such as one that comes with Twisted would have performed in this case. Seems to me that for anything that is I/O bound, the only way to really make it scale is with asynchronous programming, not threads. CPU bound is an entirely different story. Michael > > If threads are important to you, Python, even with its limitations, is > still way ahead of Ruby or Perl. At least according to the docs. > > Although I did already have a log munging code in Perl that I didn't want > to re-write, so I had a bunch of Perl processes piping data to a > multi-threaded Python process. So maybe JUST learning python is a bit > limiting. Perl really is excellent at transforming text. > > FWIW, > Barry Roberts > > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
