neon: Investigate possible bug in `im` crate
If the bug is not in the im
crate then it’s in our layer map so it’s good to check. If the bug is in the im
crate, it’s good to minimize and report/fix
More context:
_Originally posted by @bojanserafimov in https://github.com/neondatabase/neon/issues/2998#issuecomment-1381432473_
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 20 (20 by maintainers)
with the following IM patch layer bench normally completed:
Performance with patched IM and get_prev is the following:
Seems to be not “times” faster I have replaced next_back() only in one place - in
query(&self, key: i128)
. It seems to me that you wrote that get_prev() is 70% faster. On which workload?