Skip to content
This repository has been archived by the owner on Mar 14, 2019. It is now read-only.

Avoid deserializing jobs just for counts #53

Merged
merged 4 commits into from Oct 23, 2016

Conversation

davetron5000
Copy link
Contributor

Problem

To render the counts per queue on the waiting page, we fetch all jobs in that resque, deserializing them, then count them per queue, basically throwing out all the job data, which we don't need. This is super slow

Solution

Stop doing that and instead just fetch the counts, which is already supported by the backend.

@davetron5000
Copy link
Contributor Author

This leaves the "get waiting jobs" stuff around. I don't think it's being used, but I only want to do one thing at a time.

This is more to see when this deploys
@davetron5000 davetron5000 merged commit 31f29e9 into master Oct 23, 2016
@davetron5000 davetron5000 deleted the avoid-deserializing-jobs-just-for-counts branch October 23, 2016 14:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant