Skip to content
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

Priority queue does not sensibly report ram duration, queue might not page out under memory pressure #67

Closed
simonmacmullen opened this issue Mar 13, 2015 · 1 comment
Assignees
Milestone

Comments

@simonmacmullen
Copy link
Contributor

Noticed while working on #65.

The priority queue ram_duration/1 implementation takes the sum of all the ram durations of the sub-queues. That means, if a single sub-queue has a ram duration of infinity (which is very likely!) then the entire queue does.

I didn't really think that through. The point of what we're trying to do here is identify fast-moving queues so they can use more ram. Ideally each sub-queue would have its own ram duration, but in the absence of that we should probably take the minimum of the sub-queue ram durations, not the sum of them.

@dumbbell
Copy link
Member

dumbbell commented Apr 1, 2015

Since 3.5.0.

dcorbacho pushed a commit that referenced this issue May 27, 2016
Move types and auth_backend modules over from rabbitmq-server.
dcorbacho added a commit that referenced this issue Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants