Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aiohttp for long data processing #1600

Closed
ghost opened this issue Feb 8, 2017 · 3 comments
Closed

aiohttp for long data processing #1600

ghost opened this issue Feb 8, 2017 · 3 comments
Labels

Comments

@ghost
Copy link

ghost commented Feb 8, 2017

i had code which process data for long time from 5 to 10 seconds.
How aiohttp cope with such situations(tornado is not good solution)? I am choosing the suitable framework.

@fafhrd91
Copy link
Member

fafhrd91 commented Feb 8, 2017

Should be fine, but only if your code is IO bound.

@samuelcolvin
Copy link
Member

Have you considered setting up a worker to do these jobs so aiohttp can return and leave the job to happen outside the request-response cycle?

I built arq for situation exactly like this, it plays nicely with aiohttp.

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants