This full node is running on a Mac Mini M4 computer * with…
66 reactions
This full node is running on a Mac Mini M4 computer * with 24 GB of RAM. You can see that a full MLX node currently requires about 140 GB of disk storage. It took four months to go from 0 transactions to 11.7 million verified transactions. My expectation is that this full node will allow me to import any wallet with many transactions onto this full node and access the entire stable balance much faster than if I synched one data center wallet at a time (which I've done painfully for years) because this node has already validated all the transactions of every wallet. As soon as the wallet you see is done aggregating, I'll import another wallet with a high transaction count and measure how fast it stabilizes the balance.
One of the things we learned while synching this wallet is that the status page of the node was causing inappropriately high disk reads because of the large count of unspents it was reporting on. Tangled Browser version 1.25.6 addressed this by turning off some of the stats until the unspent count dropped below 100,000. #millix #tangledbrowser #millixnode #fullnode
* The wallet on this node is also used by about a dozen other public nodes in the data center that do a lot of the validation for the rest of the network. We have five wallets like this spread out over about 70 server instances.
One of the things we learned while synching this wallet is that the status page of the node was causing inappropriately high disk reads because of the large count of unspents it was reporting on. Tangled Browser version 1.25.6 addressed this by turning off some of the stats until the unspent count dropped below 100,000. #millix #tangledbrowser #millixnode #fullnode
* The wallet on this node is also used by about a dozen other public nodes in the data center that do a lot of the validation for the rest of the network. We have five wallets like this spread out over about 70 server instances.
29
9
3
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
| 382,040 mlx | |
| 114 | |
| 66 |
comments
I have had mine going for quite a few months.. Why would your event log be larger if both nodes are fully synced.
Thanks for sharing! I will compare this with what I am currently dealing with on my side with my own node!
Impressive !!
This really shows how a fully synced node can turn a painful, slow process into something efficient and scalable. Curious to see how fast the next high-transaction wallet stabilizes.
This really shows how a fully synced node can turn a painful, slow process into something efficient and scalable. Curious to see how fast the next high-transaction wallet stabilizes.
G morning
I like this endurance and the results, congrats 🎉
Thank you for sharing this.
Was affraid of the node switching from public to private , and got no help when I asked for support.
I see your screenshot and I feel well.
I have few questions about the node, if you can help me to understand few things (After my espresso 😅).
Won't be long list
I like this endurance and the results, congrats 🎉
Thank you for sharing this.
Was affraid of the node switching from public to private , and got no help when I asked for support.
I see your screenshot and I feel well.
I have few questions about the node, if you can help me to understand few things (After my espresso 😅).
Won't be long list
Great work Boss full node performance and optimization look very promising. Excited for the next test
1