slow query log: only use Instant::now
when needed + refactor
#1110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes
WorkloadType
and other refactoring.incr-select
(see below).After 7d5eb15 compared to 7d5eb1532db173c032afa6b46b013148aec132c5~1:
After this PR compared to 7d5eb1532db173c032afa6b46b013148aec132c5~1:
Run on i7-7770K, 64GB RAM.
As you can see, this recovers some of the
+26%
lost in performance such that+8.4%
is lost instead.The primary reason for the performance loss was the unconditional
Instant::now
which results in a system call.This call is now conditional on whether there's also a
threshold
.API and ABI breaking changes
None
Expected complexity level and risk
1
Testing
No semantic changes.