Understanding of Ethereum’s memorials
Ethereum, one of the most widespread blockchain platforms, is based on a complex network of nodes to store the transaction course in the form of a storage pool. This temporary storage contains unconfirmed transactions and waits for a check before they are included in a block. In view of the increasing number of transactions and blocks that are generated daily, the capacity of the storage pool reaches its limits.
How high is the maximum size of the memory pool?
The exact maximum size of the Ethereum Memory Pool is not publicly announced by the developers or the Ethereum Foundation. This information is considered proprietary and lies on every knot in the network to calculate and manage your own pool sizes. However, due to various reports, studies and developer forums, we can estimate an upper limit.
Estimation of the maximum size of the storage pool
A study by Blockcypher, a blockchain data analysis company, estimated that the Ethereum storage pool could accommodate about 1 exabyte (100 billion gigabytes) of unconfirmed transactions. This corresponds:
- 1,000 terabytes
- 10 million GB
To put this in the right light, an average Netflix film (2 hours of video content) requires about 400-500 GB storage space.
Why can the storage pool overflow?
The ability of the storage pool to store unconfirmed transactions is limited by various factors:
- Transaction volume : The faster the transaction rate is, the more blocks are generated and saved in the storage pool.
- Block time : The longer it takes for a block to be broken down and verified, the more time the processing of transactions is used before you can be included in a block.
- Network overload : As a knot in the network, the storage space is shared, overload increases and leads to slower transaction processing times.
What happens when the storage pool overflows?
If the storage pool cannot save all the unconfirmed transactions within a short time, it can overflow. This can be:
- Transaction delays : Unrued transactions can remain in the memory pool for longer periods, which delays the creation and processing of blocks.
- Increased overload : Overcrowded nodes in the network compete around the available storage space, which leads to increased transaction processing times.
Diploma
While the exact maximum size of the Ethereum storage pool is unknown, the estimates indicate that it could absorb approximately 1 exabyte of unconfirmed transactions. With increasing block rate and the network, the potential risk of overflow is also growing. It is important that nodes in the Ethereum network know their own capacity limits and efficiently manage the memory in order to avoid transaction delays and traffic jams.
In order to alleviate these risks, developers examine alternative solutions, such as: However, these measures are still in its infancy and may require considerable updates to the underlying infrastructure.
