You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.
Memcache can have a great positive impact on performance. If setup incorrectly you won't benefit much from it. It's not easy to tell whether you are properly utilizing memcache. For instance:
Is your Memcache cluster oversized / undersized?
Should you reserve some memcache storage for the different components?
a) Is it more important to cache Query Frontend stuff than index writes?
b) If yes, does it make sense to have multiple memcache clusters, each component has it's own to make sure they have dedicated storage sizes? Or is it possible to configure memcache so that each component can have it's own dedicated storage within a single cluster
Memcache can have a great positive impact on performance. If setup incorrectly you won't benefit much from it. It's not easy to tell whether you are properly utilizing memcache. For instance:
a) Is it more important to cache Query Frontend stuff than index writes?
b) If yes, does it make sense to have multiple memcache clusters, each component has it's own to make sure they have dedicated storage sizes? Or is it possible to configure memcache so that each component can have it's own dedicated storage within a single cluster
Slack discussion: https://cloud-native.slack.com/archives/CCYDASBLP/p1574096262229600
The text was updated successfully, but these errors were encountered: