We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Investigate bottleneck 14th of sep. 2018 on e-neutrons and come up with some solutions. Also, can caching searches take priority over simulations?
The text was updated successfully, but these errors were encountered:
Huh? I heard of no bottleneck - what is happening?
Sorry, something went wrong.
Viktor reported that no simulations went through, I had to restart uwsgi, but we may need a long-term solution?
Approximate scan usage during the session:
N | runs | cached | forced 21 | 44 | 64 | 5 30 | 3 | 0 | 0 50 | 3 | 2 | 0 100 | 0 | 2 | 0
This is probably not an very frequent issue, should we close this?
Looks like a timing/bottleneck issue. Postpone to 2.0
No branches or pull requests
Investigate bottleneck 14th of sep. 2018 on e-neutrons and come up with some solutions. Also, can caching searches take priority over simulations?
The text was updated successfully, but these errors were encountered: