Re: tornado.web ioloop add_timeout eats CPU

Path	csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!news-out.octanews.net!indigo.octanews.net!auth.beige.octanews.com.POSTED!not-for-mail
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	Tue, 04 Sep 2012 01:21:40 -0700
Message-ID	<7xvcfui4ff.fsf@ruckus.brouhaha.com> (permalink)
Organization	Nightsong/Fort GNOX
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock	sha1:zlnP1PO/xgJ8QsffuE2ijF/JUV4=
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Lines	7
NNTP-Posting-Date	04 Sep 2012 03:21:40 CDT
X-Complaints-To	abuse@octanews.net
X-Received-Bytes	1196
Xref	csiph.com comp.lang.python:28396

Show key headers only | 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