wal
wal copied to clipboard
rosedblabs
Write Ahead Log for LSM or bitcask storage(or any append-only write).
Calling all WAL(Write Ahead Log) users! Share a brief description of your project/use case, how WAL benefits you, and any encountered challenges. Your insights will strengthen our community and inspire...
For those has been read data, I don't want read it again. How can I mark those data bas been read. I found a `segment.Remove` method implementation in source code....
I would like to ask why fixed size blocks are used. Considering that this WAL implementation is used as bitcask storage log, the waste of storage space due to padding...
Hi, this PR contains a three-part modification. PART 1：Modify the Remove & Close function for segment.go I think the "seg.closed" for segment files should be set to "false" after calling...
Currently, wal.Read supports concurrent reads without data races only when using the exact chunk position, as it assumes that WAL is actively being written. https://github.com/rosedblabs/wal/blob/9f1a618784955f220a1f62842d21bd3ecc72e51d/wal.go#L426 However, if parallel/concurrent log replay...
To ensure that each write is persisted to disk before returning success, performing a sync() for every small concurrent write introduces excessive overhead. Should we consider adding a batch sync...
Great wal lib for learning. I saw this lib uses `github.com/valyala/bytebufferpool` so I was curious whether it really offers the best performance, or at least better than `sync.Pool`. But it...
The WAL provides PendingWrites and WriteAll methods for batch writing operations. Why isn't a WriteBatch directly provided instead? Are there any specific design considerations behind this?
Metadata
Owner
Metadata
Write Ahead Log for LSM or bitcask storage(or any append-only write).