low-gc-membuffers
low-gc-membuffers copied to clipboard
cowtowncoder
Library for creating In-memory circular buffers that use direct ByteBuffers to minimize GC overhead
Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1. Release notes Sourced from junit's releases. JUnit 4.13.1 Please refer to the release notes for details. JUnit 4.13 Please refer to the release notes...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Currently only read methods can block to wait for more data. But although implementing similar blocking for writing (appending) is more difficult, it should be doable. And when implementing queuing...
To improve interoperability, it'd be good to add `InputStream` implementations. Since it is byte-oriented, it is only applicable to byte-based buffers; and probably only streamy ones. One variation is that...
(inspired by Hal H, Alex F, on discussion for use at SFDC) --- Current chunk allocation scheme has the benefit of allowing much of the memory to be returned to...
Sometimes it makes sense to get more than one entry, up to specified maximum, with one call. Main benefit is that synchronization is only done once, and the obvious downside...
Apparently deallocation of direct-allocated ByteBuffers is bit tricky, since underlying off-heap buffers are NOT necessarily freed in timely manner, partly since there is no mechanism to force deallocation. As such...
Metadata
Owner
Metadata
Library for creating In-memory circular buffers that use direct ByteBuffers to minimize GC overhead