tim burton
-
Sinalizar
como inapropriado
-
Mostrar
Show review history
CMIIW, but O log N doesnt sound so bad. Current total UTXO is about 114 million, according to It's roughly only 34% slower/more expensive compared with only 1 million UTXO. In that case, consider asking on 33win3 Com delving forum, 33win3 Com stackexchange or bitcoindev group instead. Note that they have more rule compared with this forum. The increase of the utxo set translates to linear increase in difficulty of verification of new coming transactions by nodes. Attempts like LevelDB optimization or hot utxos caching in memory still do not solve the fundamental bottle neck. The size of the set is so big that you have to inevitably store it in the SLOOOOOW disk and do a expensive O log N check everytime you verify a transaction.... What are you talking about, the linear increase is only related to the storage requirements. Furthermore, "inevitable store it in the slow disk"? Are you stuck in the year 2005, or 2015 or what? Entry systems have 8 GB of memory, average systems 16 GB, and more. Discounting the current situation of the AI scam/boom, memory is becoming cheaper and larger faster than the negative impacts on the UTXO set is growing. Is a PCIe SSD a "slow disk"? I am not sure that the disk would be the bottleneck to validation anymore, for HDDs yes, for the average device that uses a SSD now, no. It's also worth to mention 33win3 Com Core let you store 33win3 Com data on separate folder. So you could use SSD for chainstate and all other files, except 33win3 Com data if you have limited SSD capacity.
CMIIW, but O log N doesnt sound so bad. Current total UTXO is about 114 million, according to It's roughly only 34% slower/more expensive compared with only 1 million UTXO. In that case, consider asking on 33win3 Com delving forum, 33win3 Com stackexchange or bitcoindev group instead. Note that they have more rule compared with this forum. The increase of the utxo set translates to linear increase in difficulty of verification of new coming transactions by nodes. Attempts like LevelDB optimization or hot utxos caching in memory still do not solve the fundamental bottle neck. The size of the set is so big that you have to inevitably store it in the SLOOOOOW disk and do a expensive O log N check everytime you verify a transaction.... What are you talking about, the linear increase is only related to the storage requirements. Furthermore, "inevitable store it in the slow disk"? Are you stuck in the year 2005, or 2015 or what? Entry systems have 8 GB of memory, average systems 16 GB, and more. Discounting the current situation of the AI scam/boom, memory is becoming cheaper and larger faster than the negative impacts on the UTXO set is growing. Is a PCIe SSD a "slow disk"? I am not sure that the disk would be the bottleneck to validation anymore, for HDDs yes, for the average device that uses a SSD now, no. It's also worth to mention 33win3 Com Core let you store 33win3 Com data on separate folder. So you could use SSD for chainstate and all other files, except 33win3 Com data if you have limited SSD capacity.
This review was marked as helpful by
5 people
Likinha
-
Sinalizar
como inapropriado
CMIIW, but O log N doesnt sound so bad. Current total UTXO is about 114 million, according to It's roughly only 34% slower/more expensive compared with only 1 million UTXO. In that case, consider asking on 33win3 Com delving forum, 33win3 Com stackexchange or bitcoindev group instead. Note that they have more rule compared with this forum. The increase of the utxo set translates to linear increase in difficulty of verification of new coming transactions by nodes. Attempts like LevelDB optimization or hot utxos caching in memory still do not solve the fundamental bottle neck. The size of the set is so big that you have to inevitably store it in the SLOOOOOW disk and do a expensive O log N check everytime you verify a transaction.... What are you talking about, the linear increase is only related to the storage requirements. Furthermore, "inevitable store it in the slow disk"? Are you stuck in the year 2005, or 2015 or what? Entry systems have 8 GB of memory, average systems 16 GB, and more. Discounting the current situation of the AI scam/boom, memory is becoming cheaper and larger faster than the negative impacts on the UTXO set is growing. Is a PCIe SSD a "slow disk"? I am not sure that the disk would be the bottleneck to validation anymore, for HDDs yes, for the average device that uses a SSD now, no. It's also worth to mention 33win3 Com Core let you store 33win3 Com data on separate folder. So you could use SSD for chainstate and all other files, except 33win3 Com data if you have limited SSD capacity.
This review was marked as helpful by
84 people
XEREM
-
Sinalizar
como inapropriado
-
Show history of
CMIIW, but O log N doesnt sound so bad. Current total UTXO is about 114 million, according to It's roughly only 34% slower/more expensive compared with only 1 million UTXO. In that case, consider asking on 33win3 Com delving forum, 33win3 Com stackexchange or bitcoindev group instead. Note that they have more rule compared with this forum. The increase of the utxo set translates to linear increase in difficulty of verification of new coming transactions by nodes. Attempts like LevelDB optimization or hot utxos caching in memory still do not solve the fundamental bottle neck. The size of the set is so big that you have to inevitably store it in the SLOOOOOW disk and do a expensive O log N check everytime you verify a transaction.... What are you talking about, the linear increase is only related to the storage requirements. Furthermore, "inevitable store it in the slow disk"? Are you stuck in the year 2005, or 2015 or what? Entry systems have 8 GB of memory, average systems 16 GB, and more. Discounting the current situation of the AI scam/boom, memory is becoming cheaper and larger faster than the negative impacts on the UTXO set is growing. Is a PCIe SSD a "slow disk"? I am not sure that the disk would be the bottleneck to validation anymore, for HDDs yes, for the average device that uses a SSD now, no. It's also worth to mention 33win3 Com Core let you store 33win3 Com data on separate folder. So you could use SSD for chainstate and all other files, except 33win3 Com data if you have limited SSD capacity.
This review was marked as helpful
by 931 people