I thought the idea was to limit how much someone could contribute to the network so that others can also participate and have their nodes used? I understand this is the beta, but this should be the time we’re testing how the network will function without huge centralized nodes, since that is the appeal of this project. Im sure there are a ton of people who are trying to take advantage of all these incentives and hosting an insane amount of nodes, when really we need to limit that.
The network will use whatever nodes are supplied.
Yes there is something that running a lot of nodes does make it harder for people with a few nodes to earn a fair share of test nanos.
But on the other side testing with a lot of nodes also brings in valuable data that is needed. And those people are putting in a lot of personal effort and cost, so it is a bit of a balancing act I suppose. One thing that helps balance it is that the person with a few nodes does receive proportionally higher number of tokens than the thigh earners.
Yes that was the plan for everyone to bring what they have, but in real world situations we will be seeing people run 1000 nodes for themselves, so its is a needed test. In the real world it will be too expensive to run a huge datacentre collection of nodes, so we’ll most likely not be seeing more than what is in beta except for a few out there where cost is no object. Still not compete with millions of people running 20 or more nodes each.
Hosting over 1000 nodes will be costing those people a lot more than the reward tokens they will receive. Maybe if the tokens ever get to hundreds of dollars each then they might recoup some of the time and cost they put in.
When the promotions for beta testers kicks in the people with their 1000 nodes will have less an effect than the 1000’s (hopefully) who run 10-100 nodes each.
Its a difficult one to balance and no matter what you want to do there is no way to prevent these people running 1000+ nodes. No actual mechanism that can detect it, if they want to run them.
But in the end it does provide valuable data on network performance/workings and also they help build out the network to be able to test it at scale rather than one node each and be just a couple of thousand node big
Are these data collection tools going to be removed from the final product once the network goes live? It should at least be disabled by default, but ideally completely stripped out.
Which data collection tools are your talking of?
Anything to do specifically with discord is for beta only and only being fed by Maidsafe’s nodes
The only part of the node that could be considered collecting data is the forwarding of nanos to Maidsafe for tallying. And yes that will not be in the final node software unless its just repurposed for the user to specify the wallet they want the earnings to be forwarded to. IE their account wallet
Great progress, thanks team, coders, testers and all involved.
Really looking forward to getting some nodes up soon as my electrics are finally fixed.
Update after throttling back to 10 nodes, the memory consumption per node went way up to the point where I could no longer use my daily driver effectively, so I have since turned off the remaining 10 nodes and will wait for a leaner RAM peak use per safenode update more in line with what I observed in Beta Wave 2… when I ran 15 nodes and actually snagged some nanos.
I Asked Brave AI Search Assistant for Advice and actually got a useful answer which all MS Windows 11 users should read and adjust their system accordingly:
How does a user run ms windows 11 as lean as possible in 8gb of ram to ensure there is at least 4gb of ram available to run daily applications?
To ensure at least 4GB of RAM is available for daily applications on a Windows 11 system with 8GB of RAM, follow these steps:
- Disable unnecessary startup programs:
- Press the Windows key + R, type
msconfig
, and press Enter. - In the Startup tab, review the list of programs set to launch at startup.
- Disable any unnecessary programs to reduce memory consumption.
- Adjust Windows 11’s memory allocation:
- Press the Windows key + Pause/Break, and open System Properties.
- In the Performance tab, click on “Settings” under “Memory”.
- Adjust the “Commit Charge Limit” to 4096 MB (4GB) or lower, depending on your needs.
- Close unnecessary background applications:
- Press the Ctrl + Shift + Esc keys to open Task Manager.
- Review the “Processes” tab and close any unnecessary background applications.
- Disable Windows 11’s built-in features:
- Disable Windows 11’s “Game Bar” and “Game DVR” features, as they consume system resources.
- Disable “Windows Subsystem for Linux” (WSL) if not needed, as it also uses memory.
- Update Windows 11 and drivers:
- Ensure Windows 11 is updated to the latest version.
- Update your device drivers to the latest versions, as outdated drivers can consume additional memory.
- Consider disabling Windows 11’s “Dynamic Memory” feature:
- Dynamic Memory dynamically allocates memory between applications. If you have resource-intensive applications, disabling this feature might help ensure a stable 4GB of RAM for daily use.
- To disable Dynamic Memory, create a registry key:
- Press the Windows key + R, type
regedit
, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
. - Create a new DWORD value named
DynamicMemory
and set its value to0
.
- Press the Windows key + R, type
- Monitor system performance:
- Regularly check Task Manager to ensure memory usage remains within acceptable limits.
- Adjust your settings as needed to maintain a healthy balance between system performance and memory availability.
By following these steps, you should be able to optimize Windows 11 for 8GB RAM and ensure at least 4GB of RAM is available for daily applications.
Context
support.microsoft.com
Windows 11 System Requirements - Microsoft Support
www.zdnet.com
How much RAM does your Windows 11 PC need?
windowsreport.com
High Memory Usage in Windows 11: How to Reduce it in 6 Steps
www.microsoft.com
Windows 11 Specs and System Requirements
As the devs said the ram increase is due to caching of the disk being introduced. It may not be back to what it was, but maybe trimmed. It’d be good if the caching size was a configurable feature.