I removed the sequential test for write benchmark, but the generator is still used (it's useful for example, when you want to fill an instance and execute a workload where you want to control the…
I'm not sure what kind of problem you have in mind. Can you elaborate? (mu
is held during Get
).
nope. I guess from go mod tidy
. Maybe it was only indirect before.
True, but having the sequential benchmark can provide a hint to whether the substorage should do something about the sequentiality of the keys in case sequential writes happen to be beneficial for…
done. Can we force it to be constructed properly then? (maybe hide it under an interface and have a New
function that ensures those things are actually set or return an error).