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.

Sign up for GitHub

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

Jump to bottom

Log warning when CB indices are non-contiguous #16979

Closed
jbaumanTT opened this issue Jan 22, 2025 · 0 comments
Closed

Log warning when CB indices are non-contiguous #16979

jbaumanTT opened this issue Jan 22, 2025 · 0 comments
Assignees
@jbaumanTT
Labels
feature

Comments

@jbaumanTT
Copy link
Contributor

Adding a log will make it easier to discover what programs are using non-contiguous CB indices.
@jbaumanTT jbaumanTT self-assigned this Jan 22, 2025
jbaumanTT added a commit that referenced this issue Jan 23, 2025
@jbaumanTT
#16979: Log when CB ranges aren't contiguous
06d485d 
Noncontiguous CB ranges cause performance problems for the dispatcher, because it initializes all CBs up to the max used index. Warn when programs don't do that.
jbaumanTT added a commit that referenced this issue Jan 23, 2025
@jbaumanTT
#16979: Log when CB ranges aren't contiguous
a3e4f14 
Noncontiguous CB ranges cause performance problems for the dispatcher, because it initializes all CBs up to the max used index. Warn when programs don't do that.
@jbaumanTT jbaumanTT mentioned this issue Jan 23, 2025
Merged
6 tasks
jbaumanTT added a commit that referenced this issue Jan 24, 2025
@jbaumanTT
#16979: Log when CB ranges aren't contiguous
c645503 
Noncontiguous CB ranges cause performance problems for the dispatcher, because it initializes all CBs up to the max used index. Warn when programs don't do that.
patrickroberts pushed a commit that referenced this issue Jan 25, 2025
@jbaumanTT @patrickroberts
#16979: Log when CB ranges aren't contiguous
f5d4046 
Noncontiguous CB ranges cause performance problems for the dispatcher, because it initializes all CBs up to the max used index. Warn when programs don't do that.
yieldthought pushed a commit that referenced this issue Jan 31, 2025
@jbaumanTT @yieldthought
#16979: Log when CB ranges aren't contiguous
bc00adc 
Noncontiguous CB ranges cause performance problems for the dispatcher, because it initializes all CBs up to the max used index. Warn when programs don't do that.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbaumanTT jbaumanTT

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jbaumanTT