Add test to measure performance of fetch in big interval tree. #9
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.
Noticed that latest version of Set::IntervalTree is significantly slower. Up to now was using 0.11 and was more than happy with its functionality and performance 👍
In order to illustrate the latest problems I am observing added test to measure performance of fetch in big interval tree.
When the above test is run on my PC with Intel Core i7 on latest version the result of the test for elapsed time result is about 15-18seconds
When I checkout manually e2f149c the result is usually about 10ms.
As far as I could see the problem appeared in 909461a, but since it is a fix plus refactor and my C++ skills are very very basic, I figured you will be much faster and efficient at spotting and fixing the issue.