Re: tornado.web ioloop add_timeout eats CPU

From	Paul Rubin <no.email@nospam.invalid>
Newsgroups	comp.lang.python
Subject	Re: tornado.web ioloop add_timeout eats CPU
References	<mailman.129.1346653953.27098.python-list@python.org> <f06cfff2-0367-4548-a09b-736191699f29@k3g2000pbr.googlegroups.com> <mailman.170.1346744270.27098.python-list@python.org>
Date	2012-09-04 01:21 -0700
Message-ID	<7xvcfui4ff.fsf@ruckus.brouhaha.com> (permalink)
Organization	Nightsong/Fort GNOX

Show all headers | View raw

Laszlo Nagy <gandalf@shopzeus.com> writes:
> but a threaded server cannot handle 100+ simultaneous (long running)
> requests, because that would require 100+ threads to be running.

On a reasonable server these days, 100 threads seems to be no big deal.
I've run several times that many.  I think things get ragged at a few
thousand threads.

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

tornado.web ioloop add_timeout eats CPU Laszlo Nagy <gandalf@shopzeus.com> - 2012-09-03 08:31 +0200
  Re: tornado.web ioloop add_timeout eats CPU Bryan <bryanjugglercryptographer@yahoo.com> - 2012-09-03 12:47 -0700
    Re: tornado.web ioloop add_timeout eats CPU Laszlo Nagy <gandalf@shopzeus.com> - 2012-09-04 09:30 +0200
      Re: tornado.web ioloop add_timeout eats CPU Paul Rubin <no.email@nospam.invalid> - 2012-09-04 01:21 -0700

csiph-web