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

Question: Client side cache growth #55

Open
cdelgadob opened this issue Feb 14, 2019 · 1 comment
Open

Question: Client side cache growth #55

cdelgadob opened this issue Feb 14, 2019 · 1 comment

Comments

@cdelgadob
Copy link

Hi,

I was wondering how to deal with the potential growth of the client cache based on different parameters.
I could think in:

  1. Create a new graphql client whti no cache used only for searches.
  2. Skip the cache for search queries.

What's your advise here?

Thanks

@nodkz
Copy link
Member

nodkz commented Feb 14, 2019

Frankly no exact advice. Too few income data for the proper answer.

Anyway, you need to to find a solution for resetting the cache (via timeout, number of records, size of memory, or via some interval time).

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

2 participants