I never see the Tezos node using more than CPU core even when syncing from scratch. Why is this? Is this the reason why the nodes takes forever to sync in archive mode? Are there any plans to make the node multi-threaded or more performant?
Add a comment
|
1 Answer
The performance of syncing an archive node depends on multiple factors including your hardware, network connectivity, number peers etc however one of the dominant one is the intensity of I/O operations not the number of computations by the CPU (see this question for instance). It is more likely that you would go faster by improving your storage from say hdd to ssd than by having the node go from single threaded to multithreaded.
To fasten up syncing there are several alternatives
1) use snapshots: see here and there for additional infos
2) use a different history mode : see this answer for more infos
-
1Thanks for the information but this doesn't answer my questions about only a single CPU core being used.– tezetteJul 16, 2019 at 21:10
-
@tezette the tezos node is single threaded afaik so it uses only 1 cpu core.– EzyJul 17, 2019 at 3:40
-
I am more interested in why and whether there's any plans to change it?– tezetteJul 18, 2019 at 4:08
-
@tezette what makes you think its necessart for the node to be multithreaded ?– EzyJul 19, 2019 at 5:15
-
For the same benefits we get from multithreading any application on a modern processor.– tezetteNov 15, 2019 at 2:53