A variable size buffer pool for go.
Table of Contents
- Use Case
- Advantages over GC
- Disadvantages over GC:
Use this when you need to repeatedly allocate and free a bunch of temporary buffers of approximately the same size.
Advantages over GC
Reduces Memory Usage:
- We don’t have to wait for a GC to run before we can reuse memory. This is essential if you’re repeatedly allocating large short-lived buffers.
Reduces CPU usage:
- It takes some load off of the GC (due to buffer reuse).
- We don’t have to zero buffers (fewer wasteful memory writes).
Disadvantages over GC:
- Can leak memory contents. Unlike the go GC, we don’t zero memory.
- All buffers have a capacity of a power of 2. This is fine if you either (a) actually need buffers with this size or (b) expect these buffers to be temporary.
- Requires that buffers be returned explicitly. This can lead to race conditions and memory corruption if the buffer is released while it’s still in use.
PRs are welcome!
Small note: If editing the Readme, please conform to the standard-readme specification.
MIT © Protocol Labs BSD © The Go Authors