File tree Expand file tree Collapse file tree 1 file changed +28
-0
lines changed Expand file tree Collapse file tree 1 file changed +28
-0
lines changed Original file line number Diff line number Diff line change @@ -63,6 +63,34 @@ on the same machine are:
63
63
* 320 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than
64
64
electro-mechanical disks).
65
65
66
+
67
+ ### ` mainnet `
68
+
69
+ - ` cardano-node ` database: 203 GB
70
+ - ` cardano-db-sync ` ledger state: ~ 10 GB
71
+ - ` Postgres ` database ` mainnet_13.6.0.5 ` total size: 438 GB
72
+
73
+ - ` cardano-db-sync ` RSS RAM: peaks at 20.6 GB before settling at 18.5 GB
74
+
75
+
76
+ ### ` preprod `
77
+
78
+ - ` cardano-node ` database: 12 GB
79
+ - ` cardano-db-sync ` ledger state: ~ 2 GB
80
+ - ` Postgres ` database ` preprod_13.6.0.5 ` total size: 16 GB
81
+
82
+ - ` cardano-db-sync ` RSS RAM: 3,5 GB
83
+
84
+
85
+ ### ` preview `
86
+
87
+ - ` cardano-node ` database: 12 GB
88
+ - ` cardano-db-sync ` ledger state: ~ 2 GB
89
+ - ` Postgres ` database ` preview_13.6.0.5 ` total size: 21 GB
90
+
91
+ - ` cardano-db-sync ` RSS RAM: 3,5 GB
92
+
93
+
66
94
The recommended configuration is to have the ` db-sync ` and the PostgreSQL server on the same
67
95
machine. During syncing (getting historical data from the blockchain) there is a ** HUGE** amount
68
96
of data traffic between ` db-sync ` and the database. Traffic to a local database is significantly
You can’t perform that action at this time.
0 commit comments