@@ -49,20 +49,87 @@ with the use of foreign keys from one table to another). More user friendly data
49
49
implemented using [ Postgres Views] [ PostgresView ] to implement joins between tables.
50
50
51
51
## System Requirements
52
+ ### Last update: May 2025
52
53
53
54
The system requirements for ` cardano-db-sync ` (with both ` db-sync ` and the ` node ` running
54
55
on the same machine are:
55
56
56
57
* Any of the big well known Linux distributions (eg, Debian, Ubuntu, RHEL, CentOS, Arch
57
58
etc).
58
- * 32 Gigabytes of RAM or more.
59
+ * 64 Gigabytes of RAM or more (for ` mainnet ` ) .
59
60
* 4 CPU cores or more.
60
61
* Ensure that the machine has sufficient IOPS (Input/Output Operations per Second). Ie it should be
61
62
60k IOPS or better. Lower IOPS ratings will result in slower sync times and/or falling behind the
62
63
chain tip.
63
- * 320 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than
64
+ * 700 Gigabytes or more of disk storage (preferably SSD which are 2-5 times faster than
64
65
electro-mechanical disks).
65
66
67
+
68
+ Stats for configuration:
69
+
70
+ ``` json
71
+ "insert_options" : {
72
+ "tx_cbor" : " disable" ,
73
+ "tx_out" : {
74
+ "value" : " enable" ,
75
+ "force_tx_in" : false ,
76
+ "use_address_table" : false
77
+ },
78
+ "ledger" : " enable" ,
79
+ "shelley" : {
80
+ "enable" : true
81
+ },
82
+ "multi_asset" : {
83
+ "enable" : true
84
+ },
85
+ "metadata" : {
86
+ "enable" : true
87
+ },
88
+ "plutus" : {
89
+ "enable" : true
90
+ },
91
+ "governance" : " enable" ,
92
+ "offchain_pool_data" : " enable" ,
93
+ "json_type" : " text"
94
+ }
95
+ ```
96
+
97
+ ### ` mainnet `
98
+
99
+ #### Storage
100
+ - ` cardano-node ` database size: 203 GB
101
+ - ` cardano-db-sync ` total ledger state files size: ~ 10 GB
102
+ - ` Postgres ` database ` mainnet_13.6.0.5 ` total size: 438 GB
103
+
104
+ #### RAM
105
+ - ` cardano-node ` RAM: 24 GB
106
+ - ` cardano-db-sync ` RSS RAM: 21 GB
107
+
108
+
109
+ ### ` preprod `
110
+
111
+ #### Storage
112
+ - ` cardano-node ` database size: 12 GB
113
+ - ` cardano-db-sync ` total ledger state files size: ~ 2 GB
114
+ - ` Postgres ` database ` preprod_13.6.0.5 ` total size: 16 GB
115
+
116
+ #### RAM
117
+ - ` cardano-node ` RSS RAM: 5,5 GB
118
+ - ` cardano-db-sync ` RSS RAM: 3,5 GB
119
+
120
+
121
+ ### ` preview `
122
+
123
+ #### Storage
124
+ - ` cardano-node ` database size: 12 GB
125
+ - ` cardano-db-sync ` total ledger state files size: ~ 2 GB
126
+ - ` Postgres ` database ` preview_13.6.0.5 ` total size: 21 GB
127
+
128
+ #### RAM
129
+ - ` cardano-node ` RSS RAM: 2,8 GB
130
+ - ` cardano-db-sync ` RSS RAM: 3,5 GB
131
+
132
+
66
133
The recommended configuration is to have the ` db-sync ` and the PostgreSQL server on the same
67
134
machine. During syncing (getting historical data from the blockchain) there is a ** HUGE** amount
68
135
of data traffic between ` db-sync ` and the database. Traffic to a local database is significantly
0 commit comments