Re: asyncio and blocking - an update

From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Subject	Re: asyncio and blocking - an update
Date	2016-02-12 19:19 +1100
Message-ID	<mailman.72.1455265184.22075.python-list@python.org> (permalink)
References	(2 earlier) <CAPTjJmrVCkKAEevc9TW8FYYTnZgRUMPHectz+bD=DQRphXYTpw@mail.gmail.com> <n9ha5v$pb9$1@ger.gmane.org> <CAPTjJmor8dMv2TDtq8RHQgWeSAaZgAmxK9gFth=OojhidWHs3w@mail.gmail.com> <n9hjfp$ad7$1@ger.gmane.org> <n9k4f5$p8s$1@ger.gmane.org>

Show all headers | View raw

On Fri, Feb 12, 2016 at 7:17 PM, Frank Millman <frank@chagford.com> wrote:
> Using run_in_executor() and cur.fetchall(), I experience delays of up to 2
> seconds while the task is active.
>
> Using my approach, the maximum I saw was about a tenth of a second, and that
> is because I was looking for it - a normal user would not notice. Obviously
> the task took longer, but I can live with that trade-off.

That looks like good, useful data! Cool.

ChrisA

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

Thread

Re: asyncio and blocking - an update Chris Angelico <rosuav@gmail.com> - 2016-02-12 19:19 +1100

csiph-web