diff --git a/docs/sources/setup/size/_index.md b/docs/sources/setup/size/_index.md index ed052ab517ee6..eab4648e5ae7a 100644 --- a/docs/sources/setup/size/_index.md +++ b/docs/sources/setup/size/_index.md @@ -26,13 +26,6 @@ Query resource needs can greatly vary with usage patterns and correct configurat - Large Loki clusters benefit from a disk based caching solution, memcached-extstore. Please see the detailed [blog post](https://grafana.com/blog/2023/08/23/how-we-scaled-grafana-cloud-logs-memcached-cluster-to-50tb-and-improved-reliability/) and read more about [memcached/nvm-caching here](https://memcached.org/blog/nvm-caching/). - If you’re running a cluster that handles less than 30TB/day (~1PB/month) ingestion, we do not recommend configuring memcached-extstore. The additional operational complexity does not justify the savings. -These are the node types we suggest from various cloud providers. Please see the relevant specifications in your provider documentation. -
- -
-
{{< tabs >}} {{< tab-content name="Less than 100TB/month (3TB/day)" >}} @@ -70,74 +63,9 @@ These are the node types we suggest from various cloud providers. Please see the {{< /tab-content >}} {{< /tabs >}} +

Instance Types

- - - - +These are the node types we suggest from various cloud providers. Please see the relevant specifications in the provider's documentation. +- For AWS any General Purpose machine available in your region that belongs to `M6` instance family and above for Intel chips and `T2` machine family and above for ARM chips. +- For GCP any General Purpose machine available in your region that belongs to to `E2` instance family and above. +- For memcached-extstore nodes we suggest storage optimised instances that can has NVMe storage so that the additional disk space is utilized.