chore: update system requirements

Author: ArturWieczorek

Readme.md

@@ -55,13 +55,69 @@ on the same machine are:
 
 * Any of the big well known Linux distributions (eg, Debian, Ubuntu, RHEL, CentOS, Arch
   etc).
-* 32 Gigabytes of RAM or more.
+* 64 Gigabytes of RAM or more (for `mainnet`).
 * 4 CPU cores or more.
 * Ensure that the machine has sufficient IOPS (Input/Output Operations per Second). Ie it should be
   60k IOPS or better. Lower IOPS ratings will result in slower sync times and/or falling behind the
   chain tip.
-* 320 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than
-  electro-mechanical disks).
+* Disk storage - preferably SSD which are 2-5 times faster than electro-mechanical disks.
+
+
+Stats for configuration:
+
+```json
+  "insert_options": {
+    "tx_cbor": "disable",
+    "tx_out": {
+      "value": "enable",
+      "force_tx_in": false,
+      "use_address_table": false
+    },
+    "ledger": "enable",
+    "shelley": {
+      "enable": true
+    },
+    "multi_asset": {
+      "enable": true
+    },
+    "metadata": {
+      "enable": true
+    },
+    "plutus": {
+      "enable": true
+    },
+    "governance": "enable",
+    "offchain_pool_data": "enable",
+    "json_type": "text"
+  }
+```
+
+### `mainnet`
+
+- `cardano-node` database size: 203 GB
+- `cardano-db-sync` total ledger state files size: ~ 10 GB
+- `Postgres` database `mainnet_13.6.0.5` total size: 438 GB
+
+- `cardano-db-sync` RSS RAM: peaks at 20.6 GB before settling at 18.5 GB
+
+
+### `preprod`
+
+- `cardano-node` database size: 12 GB
+- `cardano-db-sync` total ledger state files size: ~ 2 GB
+- `Postgres` database `preprod_13.6.0.5` total size: 16 GB
+
+- `cardano-db-sync` RSS RAM: 3,5 GB
+
+
+### `preview`
+
+- `cardano-node` database size: 12 GB
+- `cardano-db-sync` total ledger state files size: ~ 2 GB
+- `Postgres` database `preview_13.6.0.5` total size: 21 GB
+
+- `cardano-db-sync` RSS RAM: 3,5 GB
+
 
 The recommended configuration is to have the `db-sync` and the PostgreSQL server on the same
 machine. During syncing (getting historical data from the blockchain) there is a **HUGE** amount