You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that DB#range scans over the end of range and affect performance.
I think stop iterating after the upper limit is better.
Here is the result of my test. Key is the sequence of "0000001" to "5000000" and value is just fixed string of 2KB size. If I specify the range of first ten keys, it takes 537 seconds. This is because DB#range does not stop scanning after the key "0000010". If I specify the range of the last 2 keys, it returns quickly.
Hello.
It seems that DB#range scans over the end of range and affect performance.
I think stop iterating after the upper limit is better.
Here is the result of my test. Key is the sequence of "0000001" to "5000000" and value is just fixed string of 2KB size. If I specify the range of first ten keys, it takes 537 seconds. This is because DB#range does not stop scanning after the key "0000010". If I specify the range of the last 2 keys, it returns quickly.
Maybe, stop iterating after the end of the range would be better? (like below)
The text was updated successfully, but these errors were encountered: