Badger seeks to prefix much slower than file reads (30x), on SSD

Great. Here is the output of the badger info command. The data to reproduce the query is about 2.3GB at the moment (won’t go through email). I can share it if you have a place I can push it to.

$ badger info --dir honeyBadger-badgerdb
Listening for /debug HTTP requests at port: 8080

[     2020-08-10T18:05:08Z] MANIFEST      574 B MA
[        3 seconds earlier] 000033.sst    72 MB L1 
[        2 seconds earlier] 000034.sst    71 MB L1 
[         1 second earlier] 000035.sst    75 MB L1 
[                      now] 000036.sst    75 MB L1 
[                      now] 000037.sst   8.2 MB L1 
[       17 minutes earlier] 000028.sst    71 MB L2 
[       17 minutes earlier] 000029.sst    71 MB L2 
[       17 minutes earlier] 000004.vlog  743 MB VL
[        5 minutes earlier] 000005.vlog  1.0 GB VL
[        3 seconds earlier] 000006.vlog  224 MB VL

[EXTRA]
[2020-08-10T17:44:48Z] KEYREGISTRY    28 B

[Summary]
Level 0 size:          0 B
Level 1 size:       301 MB
Level 2 size:       142 MB
Total index size:   443 MB
Value log size:     2.0 GB

Abnormalities:
1 extra file.
0 missing files.
0 empty files.
0 truncated manifests.
badger 2020/08/10 18:05:11 INFO: All 7 tables opened in 137ms
badger 2020/08/10 18:05:11 INFO: Replaying file id: 6 at offset: 223816271
badger 2020/08/10 18:05:11 INFO: Replay took: 18.751µs