-
Notifications
You must be signed in to change notification settings - Fork 173
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
How to use the results to get or calculate throughput and latency as the paper #57
Comments
Did you solve it? |
I have the same problem. Can you give me the solution to the problem?
|
@jonghwaC no ,no one told me how to solve during this time. |
I have a similar result. So I am in small bank code analysis. "threads.emplate_back (StatusThread, sb, props [" dbname "], props [" endpoint "] ..." |
I am doing the same experiment as you, but there is no result, can we communicate? |
@jonghwaC @CryptonQQQ I got some of result of latency has been 0. |
@keruisiya @CryptonQQQ I think I should use the latency defined in StatusThread. My plan is to terminate StatusThread when all ClientThreads are terminated. |
@jonghwaC ok!thanks! If you get the right results, please let me know! |
Hi, @keruisiya , @jonghwaC Our team found this Have you checked that and did that help? Thanks, |
This document is not used to analyze the results. It's a document in ycsb. The author modified ycsb, so it can't be used to analyze the results. |
Hi @listenfound , You are right. see #49 . After all, I don't think their way of calculating latency makes sense. See the discussion in #64. There could be a finer way of doing this. Thank you for your discussion. Best wishes, |
i run ethereum's macro benchmark kv_store and run./run_bench.sh 2 4 2 10 and i got some results as follow, please help me how to use these data to calculate the throughput and latency as the paper?
Results: client_192.168.43.246: https://pastebin.com/uBvX84V3
client_192.168.43.162: https://pastebin.com/USRHRKUy
eth_log: https://pastebin.com/pZcUCTvp
how to get ?? thank you
The text was updated successfully, but these errors were encountered: