Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Differentiate between 'write ring' and 'read ring' buffers #4

Open
jaynel opened this issue Oct 18, 2013 · 0 comments
Open

Differentiate between 'write ring' and 'read ring' buffers #4

jaynel opened this issue Oct 18, 2013 · 0 comments

Comments

@jaynel
Copy link
Member

jaynel commented Oct 18, 2013

Ring buffers are great for concurrent writers because they have a natural cap on memory used and overwrite the oldest entries automatically.

Ring buffers for readers can also be great for tasks like load-balancing in a round-robin fashion by just continuously reading the next element and allowing wraparound on reads.

The current implementation deletes entries from LIFO / FIFO buffers when they are read, but not from RING buffers, but it only allows Write wraparound on RING buffers. A Read wraparound RING type needs to be introduced.

@jaynel jaynel mentioned this issue Oct 6, 2014
jaynel pushed a commit to jaynel/epocxy that referenced this issue Jan 6, 2016
TS-1178 Cache refresh item with no_value_available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant