GetMappedRange is an experimental feature introduced in FDB 7.1. It is intended to improve the client throughput and reduce latency for a commonly used traffic pattern. An experiment with Record Layer shows that this optimization can get 4x client throughput on a certain workload.
Because this feature is under active development, there have been interests and questions from the community. To summarize everything I know about it, I wrote a document and published here. It describes what this feature is for, how to use it, and the known issues (or future work).
If you have any questions, please feel free to reply to this post. It’s the best way to reach out to me and future developers of this feature.
Having read the document, this feature should fit my use case quite well. I have a custom layer that does indexing and it looks like I can easily rewrite my getv-using-index function to make use of GetMappedRange and it should improve performance significantly. It is a very common usage pattern in my app.
No questions, posting this just so that it doesn’t seem like nobody cares. We do
Got it, thanks for the report. Looking at the logic for this tenant name required check, it seems I didn’t quite complete it. As far as I know we’re not currently evaluating any use-cases that rely on both features, so I guess this slipped under the radar.
Let me try to add a test to reproduce it and then I’ll fix up the check.