From c9e7c6bced7afc7860c372797f32ac7dab00a6b8 Mon Sep 17 00:00:00 2001 From: Silvio Moioli Date: Tue, 21 May 2024 16:59:02 +0200 Subject: [PATCH] tuning: recommend minimum browser specs (#1290) * tuning: recommend minimum browser specs Signed-off-by: Silvio Moioli Co-authored-by: Marty Hernandez Avedon * fix nbsps Signed-off-by: Silvio Moioli --------- Signed-off-by: Silvio Moioli Co-authored-by: Marty Hernandez Avedon --- .../tuning-and-best-practices-for-rancher-at-scale.md | 10 ++++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 10 ++++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 10 ++++++++++ .../tuning-and-best-practices-for-rancher-at-scale.md | 10 ++++++++++ 4 files changed, 40 insertions(+) diff --git a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 50687cdd32c..9242749aa5e 100644 --- a/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/docs/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -118,3 +118,13 @@ The two main bottlenecks to [etcd performance](https://etcd.io/docs/v3.4/op-guid It's best to run etcd on exactly three nodes, as adding more nodes will reduce operation speed. This may be counter-intuitive to common scaling approaches, but it's due to etcd's [replication mechanisms](https://etcd.io/docs/v3.5/faq/#what-is-maximum-cluster-size). Etcd performance will also be negatively affected by network latency between nodes as that will slow down network communication. Etcd nodes should be located together with Rancher nodes. + +### Browser Requirements + +At high scale, Rancher transfers more data from the upstream cluster to UI components running in the browser, and those components also need to perform more processing. + +For best performance, ensure that the host running the hardware meets these requirements: + - 2020 i5 10th generation Intel (4 cores) or equivalent + - 8 GB RAM + - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 50687cdd32c..9242749aa5e 100644 --- a/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.6/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -118,3 +118,13 @@ The two main bottlenecks to [etcd performance](https://etcd.io/docs/v3.4/op-guid It's best to run etcd on exactly three nodes, as adding more nodes will reduce operation speed. This may be counter-intuitive to common scaling approaches, but it's due to etcd's [replication mechanisms](https://etcd.io/docs/v3.5/faq/#what-is-maximum-cluster-size). Etcd performance will also be negatively affected by network latency between nodes as that will slow down network communication. Etcd nodes should be located together with Rancher nodes. + +### Browser Requirements + +At high scale, Rancher transfers more data from the upstream cluster to UI components running in the browser, and those components also need to perform more processing. + +For best performance, ensure that the host running the hardware meets these requirements: + - 2020 i5 10th generation Intel (4 cores) or equivalent + - 8 GB RAM + - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 50687cdd32c..9242749aa5e 100644 --- a/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.7/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -118,3 +118,13 @@ The two main bottlenecks to [etcd performance](https://etcd.io/docs/v3.4/op-guid It's best to run etcd on exactly three nodes, as adding more nodes will reduce operation speed. This may be counter-intuitive to common scaling approaches, but it's due to etcd's [replication mechanisms](https://etcd.io/docs/v3.5/faq/#what-is-maximum-cluster-size). Etcd performance will also be negatively affected by network latency between nodes as that will slow down network communication. Etcd nodes should be located together with Rancher nodes. + +### Browser Requirements + +At high scale, Rancher transfers more data from the upstream cluster to UI components running in the browser, and those components also need to perform more processing. + +For best performance, ensure that the host running the hardware meets these requirements: + - 2020 i5 10th generation Intel (4 cores) or equivalent + - 8 GB RAM + - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less diff --git a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md index 50687cdd32c..9242749aa5e 100644 --- a/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md +++ b/versioned_docs/version-2.8/reference-guides/best-practices/rancher-server/tuning-and-best-practices-for-rancher-at-scale.md @@ -118,3 +118,13 @@ The two main bottlenecks to [etcd performance](https://etcd.io/docs/v3.4/op-guid It's best to run etcd on exactly three nodes, as adding more nodes will reduce operation speed. This may be counter-intuitive to common scaling approaches, but it's due to etcd's [replication mechanisms](https://etcd.io/docs/v3.5/faq/#what-is-maximum-cluster-size). Etcd performance will also be negatively affected by network latency between nodes as that will slow down network communication. Etcd nodes should be located together with Rancher nodes. + +### Browser Requirements + +At high scale, Rancher transfers more data from the upstream cluster to UI components running in the browser, and those components also need to perform more processing. + +For best performance, ensure that the host running the hardware meets these requirements: + - 2020 i5 10th generation Intel (4 cores) or equivalent + - 8 GB RAM + - Total network bandwith to the upstream cluster: 72 Mb/s (equivalent to a single 802.11n Wi-Fi 4 link stream, ~8 MB/s http download throughput) + - Round-trip time (ping time) from browser to upstream cluster: 150 ms or less