-
Notifications
You must be signed in to change notification settings - Fork 94
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]: Performance tuning log #1383
Comments
This comment was marked as resolved.
This comment was marked as resolved.
popcnt1
added a commit
that referenced
this issue
Feb 22, 2024
## Summary 1. move build tx out of execution bench, result: #1383 (comment) huge improvement(It's actually closer to the real server-side execution overhead) , the major cost is from tokio wake in present (need to figure out) 2. split write/query bench --------- Co-authored-by: popcnt-subodhi <subodhi@west>
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
with mem fs:
|
run bench with tx_data_size = 0, no significant improvement
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
popcnt1
pushed a commit
that referenced
this issue
Mar 3, 2024
no significant improvement: #1383 (comment)
This comment was marked as outdated.
This comment was marked as outdated.
for no_sync rocksdb (put & write_batch), I log rocksdb operation's cost and using script to output this (187us/tx):
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
execute l1 block tx for btc block after 800,000(height):
for btc block after 200,000(height) is 132.46ms: building profile effect:
|
|
too old data, move to #3031 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
platform1:
MacBook Apple M2 24GB 512GB
disk:
mem filesystem
original result (updated: #1392)
platform 2
Fedora39
12700k with optane905:
Platform 3
Google Cloud with 2TB persistent SSD
Platform 4
alicloud
Platform 5
Fedora39
Intel12700K + Solidigm D5-P5430
The text was updated successfully, but these errors were encountered: