Merge pull request #3760 from Blargian/improve_installation_guide

Improve installation guide

Author: Blargian

docs/architecture/cluster-deployment.md

@@ -6,7 +6,7 @@ title: 'Cluster Deployment'
 description: 'By going through this tutorial, you will learn how to set up a simple ClickHouse cluster.'
 ---
 
-This tutorial assumes you've already set up a [local ClickHouse server](../getting-started/install.md)
+This tutorial assumes you've already set up a [local ClickHouse server](../getting-started/install/install.mdx)
 
 By going through this tutorial, you'll learn how to set up a simple ClickHouse cluster. It'll be small, but fault-tolerant and scalable. Then we will use one of the example datasets to fill it with data and execute some demo queries.
 

docs/guides/sizing-and-hardware-recommendations.md renamed to docs/best-practices/sizing-and-hardware-recommendations.md

@@ -69,7 +69,14 @@ As an example, when using M-type CPUs, we recommend provisioning 100GB of memory
 
 ## Memory {#memory}
 
-Like your choice of CPU, your choice of memory to storage ratio and memory to CPU ratio is dependent on your case. In general, however, the more memory you have, the faster your queries will run. If your use case is sensitive to price, lower amounts of memory will work as it is possible to enable settings ([`max_bytes_before_external_group_by`](/operations/settings/settings#max_bytes_before_external_group_by) and [`max_bytes_before_external_sort`](/operations/settings/settings#max_bytes_before_external_sort)) to allow spilling data to disk, but note that this may significantly affect query performance.
+Like your choice of CPU, your choice of memory to storage ratio and memory to CPU ratio is dependent on your use-case.
+
+The required volume of RAM generally depends on:
+- The complexity of queries.
+- The amount of data that is processed in queries.
+
+In general, however, the more memory you have, the faster your queries will run. 
+If your use case is sensitive to price, lower amounts of memory will work as it is possible to enable settings ([`max_bytes_before_external_group_by`](/operations/settings/settings#max_bytes_before_external_group_by) and [`max_bytes_before_external_sort`](/operations/settings/settings#max_bytes_before_external_sort)) to allow spilling data to disk, but note that this may significantly affect query performance.
 
 ### What should the memory to storage ratio be? {#what-should-the-memory-to-storage-ratio-be}
 

docs/deployment-guides/horizontal-scaling.md

@@ -30,12 +30,12 @@ This example architecture is designed to provide scalability.  It includes three
 |`chnode3`|Used for ClickHouse Keeper quorum|
 
 :::note
-In production environments we strongly recommend that ClickHouse Keeper runs on dedicated hosts.  This basic configuration runs the Keeper functionality within the ClickHouse Server process. The instructions for deploying ClickHouse Keeper standalone are available in the [installation documentation](/getting-started/install.md/#install-standalone-clickhouse-keeper).
+In production environments we strongly recommend that ClickHouse Keeper runs on dedicated hosts.  This basic configuration runs the Keeper functionality within the ClickHouse Server process. The instructions for deploying ClickHouse Keeper standalone are available in the [installation documentation](/getting-started/install/install.mdx).
 :::
 
 ## Install {#install}
 
-Install Clickhouse on three servers following the [instructions for your archive type](/getting-started/install.md/#available-installation-options) (.deb, .rpm, .tar.gz, etc.). For this example, you will follow the installation instructions for ClickHouse Server and Client on all three machines.
+Install Clickhouse on three servers following the [instructions for your archive type](/getting-started/install/install.mdx) (.deb, .rpm, .tar.gz, etc.). For this example, you will follow the installation instructions for ClickHouse Server and Client on all three machines.
 
 ## Editing configuration files {#editing-configuration-files}
 

docs/deployment-guides/replicated.md

@@ -38,9 +38,9 @@ In production environments, we strongly recommend using *dedicated* hosts for Cl
 
 ## Install {#install}
 
-Install ClickHouse server and client on the two servers `clickhouse-01` and `clickhouse-02` following the [instructions for your archive type](/getting-started/install.md/#available-installation-options) (.deb, .rpm, .tar.gz, etc.).
+Install ClickHouse server and client on the two servers `clickhouse-01` and `clickhouse-02` following the [instructions for your archive type](/getting-started/install/install.mdx) (.deb, .rpm, .tar.gz, etc.).
 
-Install ClickHouse Keeper on the three servers `clickhouse-keeper-01`, `clickhouse-keeper-02` and `clickhouse-keeper-03` following the [instructions for your archive type](/getting-started/install.md/#install-standalone-clickhouse-keeper) (.deb, .rpm, .tar.gz, etc.).
+Install ClickHouse Keeper on the three servers `clickhouse-keeper-01`, `clickhouse-keeper-02` and `clickhouse-keeper-03` following the [instructions for your archive type](/getting-started/install/install.mdx) (.deb, .rpm, .tar.gz, etc.).
 
 ## Editing configuration files {#editing-configuration-files}
 

docs/getting-started/example-datasets/nypd_complaint_data.md

@@ -21,8 +21,7 @@ The dataset used in this guide comes from the NYC Open Data team, and contains d
 
 ## Prerequisites {#prerequisites}
 - Download the dataset by visiting the [NYPD Complaint Data Current (Year To Date)](https://data.cityofnewyork.us/Public-Safety/NYPD-Complaint-Data-Current-Year-To-Date-/5uac-w243) page, clicking the Export button, and choosing **TSV for Excel**.
-- Install [ClickHouse server and client](../../getting-started/install.md).
-- [Launch](../../getting-started/install.md#launch) ClickHouse server, and connect with `clickhouse-client`
+- Install [ClickHouse server and client](../../getting-started/install/install.mdx)
 
 ### A note about the commands described in this guide {#a-note-about-the-commands-described-in-this-guide}
 There are two types of commands in this guide: