the logtail protocol should be stable before major logtailreplay package refactors, otherwise we can't ensure the semantic correctness during the refactor about changing from copy-on-write to multi-version implementation.
I doubt whether the bottleneck is really at logtail replaying. I'll do some executing tracer works to measure it.
Implementing a concurrent btree will not be done in the short term.
The logtailreplay package needs unit tests to ensure semantic correctness and performance measuring.
Is there an existing issue for the same tech request?
Does this tech request not affect user experience?
What would you like to be added ?
Why is this needed ?
No response
Additional information
No response