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

perf(s3storage/wal): use PriorityQueue rather than TreeSet #753

Merged
merged 2 commits into from
Nov 29, 2023

Conversation

Chillax-0v0
Copy link
Contributor

No description provided.

@Chillax-0v0 Chillax-0v0 added enhancement New feature or request s3stream wal the WAL of S3 stream labels Nov 28, 2023
@Chillax-0v0 Chillax-0v0 self-assigned this Nov 28, 2023
Copy link

codecov bot commented Nov 28, 2023

Codecov Report

Merging #753 (7899e55) into main (f52f72a) will decrease coverage by 0.07%.
Report is 3 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #753      +/-   ##
============================================
- Coverage     57.41%   57.35%   -0.07%     
+ Complexity     1225     1224       -1     
============================================
  Files           131      131              
  Lines          8047     8047              
  Branches        736      736              
============================================
- Hits           4620     4615       -5     
- Misses         3030     3035       +5     
  Partials        397      397              
Components Coverage Δ
RocketMQ Broker ∅ <ø> (∅)
RocketMQ Common 5.80% <ø> (ø)
RocketMQ Controller 54.60% <ø> (ø)
RocketMQ Proxy 42.75% <ø> (ø)
RocketMQ Store 76.96% <ø> (-0.25%) ⬇️
RocketMQ Stream ∅ <ø> (∅)
RocketMQ Metadata 35.44% <ø> (ø)

see 8 files with indirect coverage changes

Signed-off-by: Ning Yu <[email protected]>
@superhx superhx merged commit ba18c3c into main Nov 29, 2023
13 of 16 checks passed
@superhx superhx deleted the feat-s3-stream-wal-more-metrics branch November 29, 2023 01:38
}
ByteBufMetricsStats.getHistogram("wal_block").update(data.readableBytes());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The memory usage is predictable, there is no need to record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request s3stream wal the WAL of S3 stream
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants