You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.
Jolog currently spawns CpuCount*2 threads on startup. For many programs, we don't need that many threads so starting them is wasteful. Instead, start with one worker thread. Each time the manager thread prepares to block (because it's outpaced the workers), start a new thread. At most CpuCount*2 workers should ever run.
There are many more optimizations we could make to tune worker count based on CPU usage and blocking IO usage, but this small adjustment is easy and should help quite a bit.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Jolog currently spawns
CpuCount*2
threads on startup. For many programs, we don't need that many threads so starting them is wasteful. Instead, start with one worker thread. Each time the manager thread prepares to block (because it's outpaced the workers), start a new thread. At mostCpuCount*2
workers should ever run.There are many more optimizations we could make to tune worker count based on CPU usage and blocking IO usage, but this small adjustment is easy and should help quite a bit.
The text was updated successfully, but these errors were encountered: