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.

Sign up for GitHub

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

Jump to bottom

Optimize ThreadPool usage, make more use of async IO #7140

Closed

fm3 opened this issue Jun 14, 2023 · 0 comments · Fixed by #7139

Assignees

Labels

Member

fm3 commented Jun 14, 2023

We should take a closer look at the threadpool configuration, compare https://www.playframework.com/documentation/2.8.x/ThreadPools

We should probably get rid of the Global Execution Context
We should probably increase the number of threads in the play thread pool, because we have some blocking IO
We should reduce the amount of blocking IO

What may be blocking

talking to postgres (though slick claims async, maybe it has its own thread pool?)
talking to redis (there may be alternative clients, such as lettuce or salad (I’m not making these up))
talking to dataset storage via https (fixed in Async IO for HttpsDataVault, Fox Error Handling #7137)
talking to google cloud storage, s3
talking to file system
talking to fossildb (wip in Larger play thread pool, async fossil client #7139)

fm3 added the enhancement label

fm3 mentioned this issue

Larger play thread pool, async fossil client #7139

Merged

12 tasks

philippotto assigned fm3

fm3 closed this as completed in #7139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment