graphql-compose-elasticsearch icon indicating copy to clipboard operation
graphql-compose-elasticsearch copied to clipboard

Question: Client side cache growth

Open cdelgadob opened this issue 6 years ago • 1 comments

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

cdelgadob avatar Feb 14 '19 09:02 cdelgadob

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).

nodkz avatar Feb 14 '19 13:02 nodkz