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

2 Questions on fastcache #12

Closed
hiqinternational opened this issue Jun 3, 2019 · 3 comments
Closed

2 Questions on fastcache #12

hiqinternational opened this issue Jun 3, 2019 · 3 comments
Labels
question Further information is requested

Comments

@hiqinternational
Copy link

hiqinternational commented Jun 3, 2019

There is no cache expiration. Entries are evicted from the cache only on cache size overflow. Entry deadline may be stored inside the value in order to implement cache expiration.

does this mean FIFO or ALL entries are evicted from the cache?

  1. 64kb chunks are designed for all values (e.g. 512b values, 1k value etc) or purely for 64kb values only?
    e.g. if my values are mostly 512bytes in sizes, should I lower it to 512b instead manually inside the program? and if so, should I also change the values for SetBig (distinct API)?
@valyala valyala added the question Further information is requested label Jun 4, 2019
@valyala
Copy link
Collaborator

valyala commented Jun 4, 2019

  1. Entries are evicted in FIFO-like order.
  2. 64kb chunks are designed for storing values of all sizes up to 64kb. For bigger values SetBig API must be used.

@valyala
Copy link
Collaborator

valyala commented Jun 4, 2019

There is also pending pull request that adds timeouts - see #10

@hiqinternational
Copy link
Author

appreciate the quick response. thanks for fasthttp too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants