Currently we materialize the key in the internal call to seekForKeyString(...), discard the result, and materialize the key again using curr(...). A simple refactoring would allow us not to duplicate work. This should lead to a modest, but non-trivial performance improvement, at least for workloads where the index fits in memory. If the index entries need to be read from disk, then the cost of the extra materialization is rendered trivial.