OK thanks. I guess this benchmark must be run on a large-enough index that it doesn't fit entirely in RAM already anyway? When I ran it locally using the vanilla benchmark instructions, I believe the generated index was quite small (wikimedium10k). At any rate, I don't have any specific use case yet, just thinking about some possibilities related to primary key lookup and came across this anomaly. Perhaps at least it deserves an annotation on the benchmark graph.
- benchmark drop for PrimaryKey Michael Sokolov
- Re: benchmark drop for PrimaryKey Adrien Grand
- Re: benchmark drop for PrimaryKey David Smiley
- Re: benchmark drop for PrimaryKey Michael Sokolov
- Re: benchmark drop for PrimaryKey Michael Sokolov
- Re: benchmark drop for PrimaryKey Adrien Grand
- Re: benchmark drop for PrimaryKe... Michael Sokolov
