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

Add rocksdb_rows_read|inserted|updated|deleted #40

Closed
hermanlee opened this issue Sep 28, 2015 · 2 comments
Closed

Add rocksdb_rows_read|inserted|updated|deleted #40

hermanlee opened this issue Sep 28, 2015 · 2 comments
Assignees
Labels

Comments

@hermanlee
Copy link
Contributor

Issue by yoshinorim
Friday May 15, 2015 at 21:49 GMT
Originally opened as MySQLOnRocksDB#65


We can get these from table statistics but will still be very useful if exposing as status variables. Calculating and getting these stats need to be fast enough.

@hermanlee
Copy link
Contributor Author

Performing the row_counters need to be efficient. Using atomic counters across multiple threads (especially rows_read) can cause too much contention. Look at innodb's srv_stats_t structure on an example of how ib_counters_t were implemented.

@santoshbanda
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants