Replies: 1 comment 1 reply
-
It needs in order of importance:
I'm curious how much ram it will use in the end, if you could tell then it would be really helpful as the number on Mac OS isn't the real one. Basically kibo computes the full state of the chain for each block to compute all of the data which is quite a lot of resource and does it, in chunks of blocks in 1 month before flushing (exporting) everything to disk and starting the next chunk. I have plans to make this window (of 1 month) variable to be possible to use the program on machines with less RAM (smaller window, will be slower though) or more RAM (bigger window, to finish faster). Hope this answers your questions |
Beta Was this translation helpful? Give feedback.
-
Just wondered what resources kibo needs most, and any potential bottlenecks when parsing the data.
I see that similar to IBD of chain data, there's more data to parse in more recent blocks.
My system seems to utilize about 13-14GB of memory.
Occassionaly CPU spikes, but consistently is around 10-25% using all cores (Ryzen 9 6900HX)
Disk I/O seems quite high utilization at 1.5-2GiB/s Read and1-2.5MiB/s Write.
So far, so good! Thanks for opening up a discussion area.
Beta Was this translation helpful? Give feedback.
All reactions