-
Notifications
You must be signed in to change notification settings - Fork 4k
DO NOT MERGE Remove CQv1 #14769
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
base: main
Are you sure you want to change the base?
DO NOT MERGE Remove CQv1 #14769
Conversation
It was only used by CMQs and they have been removed a while back.
| %% @todo This can be heavily simplified: if the message falls into delta, | ||
| %% add it there. Otherwise just add it to q3 in the correct position. | ||
| %% @todo I think if the message falls within Q3 we must add it back there, | ||
| %% otherwise there's nothing to do? Except update stats. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo
| St#vqstate{?UP(len, ram_msg_count, +1), | ||
| ?UP(bytes, +msg_size(MS)), ?UP(unacked_bytes, -msg_size(MS))}. | ||
|
|
||
| %% TODO!!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo
| sets:union(MOD, Confirmed) }) | ||
| end). | ||
|
|
||
| %% @todo Having to call run_backing_queue is probably reducing performance... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo
| %% queue implementation itself. | ||
| -export([pre_publish/7, flush_pre_publish_cache/2, | ||
| sync/1, needs_sync/1, flush/1, | ||
| %% @todo TODO |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
todo
We avoid an extra unnecessary message to the queue.
And drop all terminology from antique CQ. Some terminology remains in the backing_queue_SUITE, to be addressed later.
These metrics make a lot less sense in today's CQ implementation. Today messages are either in memory about to be sent to the consumer, or on disk because they are further down the queue. Messages are no longer paged out to disk depending on memory pressure. So knowing how many transient messages are on disk is not as important. In practice almost all of them will be.
It duplicates the ?QUEUE:len and the #q_tail.count which together provide the same value.
No description provided.