Header is not cached, lookups may take 3 seeks rather than claimed 2.

[patrick-higgins]

The 2kB header is not stored in cdb.Cdb, so find() calls c.readNums((h << 3) & 2047) on the first lookup after each call to FindStart(). If the OS cache was flushed, this could lead to 3 seeks rather than 2.

[jbarham]

Hmm, in practice ISTM that the header should be hot given that it's accessed on every read and therefore very unlikely to be flushed.

[patrick-higgins]

Yeah, I guess just because you store something in your program's memory, it might get swapped and result in 3 seeks, too. Anyway, caching the header would also reduce the number of byte to integer conversions, though compared to a seek these may not be worth worrying about.

[jbarham]

Integer conversions are negligible compared to disk I/O so I'll leave it as is for now.