cronos icon indicating copy to clipboard operation
cronos copied to clipboard

Problem: Pruned node syncs really slow and uses more space

Open jasoncsli opened this issue 2 years ago • 3 comments

# From the doc
Pruned node (setting pruning=everything) 
Storage: ~25G* 
RAM: 4 GB (LevelDB) or 64G RAM (RocksDB)*** 
CPU: 4-core
# config.toml
db_backend = "goleveldb"

# app.toml
pruning="everything"

# mem
free -h
              total        used        free      shared  buff/cache   available
Mem:           15Gi       9.5Gi       185Mi       0.0Ki       5.6Gi       5.6Gi
Swap:            0B          0B          0B

# cpu and iostat are seems ok

# disk
/dev/nvme0n1    1007G  468G  488G  49% /data

I have been using cronosd (v0.6.10) to syncs from 1 to 2,693,800 for over one week. It seems too slow for syncing. Is it normal for a Pruned node? It has used 468G disk space which is more than 25G. Am I doing something wrong? Thx.

jasoncsli avatar Feb 17 '23 02:02 jasoncsli

how large is the application.db, because pruning setting only affect that one, the storage requirement in doc maybe out of date.

yihuang avatar Feb 17 '23 02:02 yihuang

@yihuang Block Height: 2533702 101G ./application.db

jasoncsli avatar Feb 21 '23 02:02 jasoncsli

@yihuang

Block Height: 2533702

101G ./application.db

not much we can do in current version, you can try scale up the machine, especially increase amount of ram. In future version we'll have some dramatic improvement at db level.

yihuang avatar Feb 21 '23 06:02 yihuang