with regression test and benchmark

conserve memory (unless something indicates that raising this would be useful)

it was *okay* in drop since we were dropping in spawn_blocking tasks, but kind of setting things up for problems later.

also all the option stuff to let it be take()n was gross and now it's gone

not generic over storage anymore, yay

seems like it's good on the write side

unclear if there's a win on reads

you're not the fastest but you are the most well-behaved.

it's fast but it's being allowed to use a lot of mem

it works? it's fast?

eh

redb blows up the disk a bit unsurprisingly

fast but this might be buffering in mem? need to verify.

just slightly slower than redb atm

small (~3%) perf hit for this, which is fine

righttttttttttt

pretty much no perf impact still