[WIP] Add tracing and analyzing for iterator next/prev count #4561
Conversation
…hen any of the Get or Put is called
…ing and analyzing
…ount per second, tested by trace_analyzer_test
|
Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours may need attention. You currently have a CLA record in our system (either from being a fromer employee or from a previous collaboration) that may require an update. Please email cla@fb.com with your name, GitHub id, email address, screenshot of your attempt to sign the CLA at code.facebook.com/cla, and whether you are are a former employee, so we can update your status. Note that if you feel this message is in error, occasionally the message appears transiently and the CLA bot will catch up and comment that your CLA is still in tact. So please give a few minutes before sending the email. Thank you. |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
1 similar comment
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Count the number of Next or Prev called in the iterator by Seek or SeekForPrev. Analyze the trace with the corresponding content.
Test plan: test by db_bench and real workload