-
Notifications
You must be signed in to change notification settings - Fork 217
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
Main Branch Performance Monitoring #1063
Labels
Comments
release/4.x@83760 aka 20240417.1 vs main ewma over 145 builds from 81301 to 83718 Click to see tablemain
|
achamayou
changed the title
Master Performance Monitoring
Main Branch Performance Monitoring
Feb 5, 2021
We likely won't restore cimetrics, and are looking at other options with a lower maintenance cost. Follow up in #6126 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tracking CCF performance on main, meant to stay open permanently for discussion, explanation of improvements/regression that isn't specific to a single PR etc.
To discuss improving the monitoring implementation itself, please use jumaffre/cimetrics#73
End to end perf test names follow the pattern:
hist
(historical queries),ls
(logging sample),tpcc
(TPC-C benchmark)js
, orfull_js
, to indicate the app is written in javascript, and contains a large amount of dependenciesjwt
to indicate JWT are used for authentication, rather than client certificatesvirtual
orsgx
for nowcft
nowmem
, indicating that the metric is the peak memory usage in bytes, rather than the average throughput in tx/smt
means that the test was run with multiple threads (2 workers + 1 dispatcher in the current config)Tests run with Piccolo start with
pi
.Other tests are most microbenchmarks, in tx/s on the CHAMP or RB maps. The commit latency ratio is an end to end test indicating how closely commit latency trails the signature interval.
The text was updated successfully, but these errors were encountered: