-
Notifications
You must be signed in to change notification settings - Fork 2
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
Blazegraph upload tasks should be added to it's own queue #247
Comments
8adb064 looks like the wrapper causes the enqueue call in spfy.py to try and enqueue the return from the database upload. Making changes.
|
Working as of 1a3a117 |
Merged in #252 |
This was referenced Nov 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, every call of
datastruct_savvy()
callsupload_graph()
separately; with a large number of workers, this might be causing Blazegraph to hang up when running in corefacility.The way to solve this would be to merge a few of the current queues:
priority
is currently used to run blazegraph queries for the frontendblazegraph
is currently used to reserve spfyids for uploaded filesmultiples
(for RGI) andsingles
(for ECTyper) can each invoke theupload_graph()
function and cause simultaneous uploading of result graphs.There are a number of permutations for this, but for now I'm going to try and just group
3.
into their own queue. This is because2.
is fairly valuable since all tasks are dependent on it, thus we want to keep it separate. Ideally, by merging3.
and only having one worker on it, we can avoid overloading Blazegraph.Few approaches to do this:
datastruct_savvy()
task as the end task. (Again, still waiting on multi-job deps Multi dependencies (my take) rq/rq#856)I'm going to go with
2.
as it will be fast to dev. and test this theory; we can also use the decorators to eventually build full job classes.The text was updated successfully, but these errors were encountered: