Revert previous behavior of internal_key_skipped_count
Summary: With recent commit 33e0c93826fd45640b24324a642ca03d8b9ef123, db iterator skips perf context counter internal_key_skipped_count when blindly issuing internal Next(). Now increment the counter by one when issuing this Next() Test Plan: Run all existing tests Reviewers: rven, yhchiang, IslamAbdelRahman, kradhakrishnan, igor, anthony Reviewed By: anthony Subscribers: yoshinorim, leveldb, dhruba Differential Revision: https://reviews.facebook.net/D51465
This commit is contained in:
parent
481f9edb15
commit
459c7fba36
@ -193,6 +193,7 @@ void DBIter::Next() {
|
|||||||
// If the current key is a merge, very likely iter already points
|
// If the current key is a merge, very likely iter already points
|
||||||
// to the next internal position.
|
// to the next internal position.
|
||||||
iter_->Next();
|
iter_->Next();
|
||||||
|
PERF_COUNTER_ADD(internal_key_skipped_count, 1);
|
||||||
}
|
}
|
||||||
|
|
||||||
// Now we point to the next internal position, for both of merge and
|
// Now we point to the next internal position, for both of merge and
|
||||||
|
Loading…
x
Reference in New Issue
Block a user