Dust Expiry: Clean the UTXO set from spam

Posted by moonsettler

Sep 21, 2025/20:35 UTC

Recent experiments focusing on the impact of syncing on ramdisk have shed light on the performance bottlenecks in blockchain node operations, particularly highlighting that when sufficient RAM is available, the efficiency of syncing processes tends to be constrained more by CPU and network limitations rather than IO costs. This observation underscores a critical inefficiency within the current design, where despite the availability of multiple CPU cores, the lack of parallelization leads to scenarios where typically only one core is fully utilized at any given time. This limitation becomes especially apparent when operating below the assumevalid height with default settings, pointing towards a systemic underutilization of available computational resources.

Furthermore, the introduction of Utreexo, aimed at reducing the RAM needed for fast validation, inadvertently does not contribute significantly toward enhancing the parallelization of these operations. Instead, its role is primarily confined to managing memory requirements more efficiently. The observations also reveal that the synchronization process leans heavily on CPU resources because the UTXO (Unspent Transaction Output) set remains within the bounds of available, unused RAM, making larger database cache (dbcache) settings redundant for nodes. This scenario is partly due to opportunistic write-through memory caching mechanisms employed by operating systems, which manage to keep the sync process CPU-bound as long as the UTXO set can be accommodated within the system's unused RAM.

These insights underscore a pressing need for reevaluating the architectural approaches to blockchain node synchronization, emphasizing the importance of developing more sophisticated parallelization techniques. By addressing these challenges, there is potential to significantly improve the efficiency and speed of blockchain operations, thereby enhancing overall system performance in environments where hardware resources are not a limiting factor.

Link to Raw Post

Thread Summary (33 replies)

May 20 - Sep 21, 2025

Message History

34 messages

RobinLinus Original Post
May 20, 2025/01:53 UTC
orangesurf
May 20, 2025/04:25 UTC
RobinLinus
May 20, 2025/05:43 UTC
anons
May 20, 2025/05:45 UTC
RobinLinus
May 20, 2025/06:04 UTC
garlonicon
May 20, 2025/06:16 UTC
RobinLinus
May 20, 2025/06:22 UTC
garlonicon
May 20, 2025/06:30 UTC
RobinLinus
May 20, 2025/07:11 UTC
garlonicon
May 20, 2025/07:42 UTC
jsarenik
May 20, 2025/08:45 UTC
gmaxwell
May 20, 2025/10:05 UTC
sjors
May 20, 2025/10:57 UTC
gmaxwell
May 20, 2025/11:09 UTC
RobinLinus
May 20, 2025/13:10 UTC
sipa
May 20, 2025/13:40 UTC
RobinLinus
May 20, 2025/15:35 UTC
gmaxwell
May 20, 2025/23:01 UTC
aurelian_btc
May 20, 2025/23:28 UTC
gmaxwell
May 20, 2025/23:46 UTC
RobinLinus
May 21, 2025/02:31 UTC
gmaxwell
May 21, 2025/03:48 UTC
ajtowns
May 21, 2025/10:44 UTC
gmaxwell
May 21, 2025/21:59 UTC
RobinLinus
May 22, 2025/02:37 UTC
gmaxwell
May 22, 2025/07:59 UTC
ajtowns
May 23, 2025/08:34 UTC
ajtowns
May 23, 2025/08:56 UTC
gmaxwell
May 23, 2025/08:58 UTC
gmaxwell
May 23, 2025/09:02 UTC
moonsettler
May 23, 2025/16:58 UTC
gmaxwell
May 24, 2025/02:50 UTC
moonsettler
May 24, 2025/16:48 UTC
Bitcoin Logo

TLDR

Join Our Newsletter

We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.

Explore all Products

ChatBTC imageBitcoin searchBitcoin TranscriptsSaving SatoshiDecoding BitcoinWarnet
Built with 🧡 by the Bitcoin Dev Project
View our public visitor count

We'd love to hear your feedback on this project.

Give Feedback