4 ms·
Sometime in 2017/18 it has been found that one of the biggest bottlenecks for the network were propagation speeds and that those were largely weighed down by di
by vvpan 5y ago
Sometime in 2017/18 it has been found that one of the biggest bottlenecks for the network were propagation speeds and that those were largely weighed down by disk writes. Thus pretty much the whole network switched to SSDs and things improved tremendously. Some other networks have implemented stateless clients and Ethereum has been working on going in that direction for a while with a lot of effort being dedicated to it this year specifically.
- eminence32 5y agoDoes the node need bulk write speeds? or does it need fast IO ops per second?
- trianglesphere 5y agoIt needs low latency. There is a huge amount of inherently sequential lookups in the state (~9 leveldb lookups per 1 state acess in a smart contract) and you can't store the state in RAM on most consumer hardware.
- jlokier 5y agoIt's read as well as write IOPS and seek time. The Ethereum state database uses hashes as keys and is larger than anyone's reasonable amount of RAM. So most accesses are all over the database in terms of physical location, and it can't be cached in RAM effectively. There is various work to improve this, but the basic architecture does depend on random access storage to a great extent.
- nly 5y agoDoesn't make sense. Most people have faster spinning rust write speeds than they do internet bandwidth. Unless the client is generating a lot of data client side, how can writes ever be a problem? Just buffer appropriately
- deleted 5y ago[deleted]
- delaaxe 5y agoIt's not like clients just download blobs and dump them on disk. They download programs that they execute and then store the updated state on disk