Edited By
Nicolas Garcia
Users participating in Tari merge-mining are raising alarms about memory and disk space requirements. As of June 2025, comments from the community highlight substantial challenges running a stable node, leading to frustration among miners.
The consensus among miners is that additional memory and stable performance are significant pain points when running a Tari node.
Many participants report needing 16-24 GB of RAM just to keep the node operational. One miner stated, "Took me 24GB of RAM for me to get the node decently stable." This sentiment is echoed by others who warn that anything less than 16 GB might lead to crashes, with one user claiming "I had to restart the node to make it usable again."
Interestingly, some highlighted serious memory leaks, implying that even large allocations often prove inadequate. One frustrated participant remarked, "You would need about 1TB of RAM to run the app for more than a few hours."
In terms of disk space, users indicated that the requirements are fairly light compared to older systems. Current estimates hover around 10-15 GB for storage,
though continued growth may change this situation in the future.
Users generally find disk requirements manageable.
Most suggest that while the software uses bandwidth, it is not an immediate concern for many operators.
Comments suggest ongoing issues may warrant further updates from developers, as one user put it, "Good luck, I have not found a way of having a stable and working Tari node. It's just ass."
Sentiments range from frustration to acceptance. Many users express a prevailing negativity regarding the stability of the nodes, with little to no positives reported about long-term functions. The overhead for running a successful node belies the potential benefits, leading to a wider discussion about the software's viability amidst these hurdles.
Key Highlights:
β‘ Most users recommend 16 GB RAM as minimal for stability.
β οΈ High memory usage and leaks lead to frequent restarts.
π¦ Disk space is not a major concern, averaging 10-15 GB.
As the Tari community continues to grapple with these technical challenges, the question remains: how will developers address these significant hurdles to improve user experience and reliability?
In the coming months, there's a strong chance that Tari will prioritize addressing memory and disk space issues, given the rising frustrations from participants. Developers may look into optimizing the code to reduce memory leaks, thereby enhancing performance without excessive RAM requirements. Experts estimate around a 60-70% likelihood that updates aimed at stabilizing node operations could be released by early 2026. Implementing these improvements could significantly elevate the user experience, but continued reliance on subpar performance might push some users to explore alternative platforms, making it crucial for Tari to act decisively.
This situation parallels the late 1990s dot-com boom, where excitement fueled rapid growth, yet many tech startups struggled with infrastructure limitations. Just as countless early innovators needed to refine their technologies to fulfill customer expectations, Tari faces similar growing pains. The ambitious goals around merge-mining mirror early internet companies that often oversold functionalities, only to face backlash when they fell short. As those companies eventually adapted, many succeeded in establishing a robust digital economy, suggesting a pathway forward for Tari if they can learn from those earlier lessons.