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

When managedLedgerNewEntriesCheckDelayInMillis=0, avoid the context switch #10660

Merged
merged 1 commit into from
May 21, 2021

Conversation

merlimat
Copy link
Contributor

Motivation

When managedLedgerNewEntriesCheckDelayInMillis=0 is configured in broker.conf, in order to reduce the worst case for end-to-end latency, we should also avoid the context switch and paying the latency price for it.

@merlimat merlimat added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label May 20, 2021
@merlimat merlimat added this to the 2.8.0 milestone May 20, 2021
@merlimat merlimat self-assigned this May 20, 2021
@codelipenghui codelipenghui merged commit 5410d9c into apache:master May 21, 2021
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
…witch (apache#10660)

### Motivation

When `managedLedgerNewEntriesCheckDelayInMillis=0` is configured in broker.conf, in order to reduce the worst case for end-to-end latency, we should also avoid the context switch and paying the latency price for it.
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
…witch (apache#10660)

### Motivation

When `managedLedgerNewEntriesCheckDelayInMillis=0` is configured in broker.conf, in order to reduce the worst case for end-to-end latency, we should also avoid the context switch and paying the latency price for it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants