No no, a scammer had posted a link in Discord to a scam Discord group, the site was not hacked. Someone deleted the link or the scammer deleted it himself so as not to get banned.
Privacy. Security. Freedom
2 Likes
Well its time, and no word yet.
1 Like
@joshuef I looked at the release changes but am not really getting a good idea of what’s new.
Could you please 
give us a breakdown of what’s new or changed, improved?
I am running the same amount of nodes as before but seemingly being seen as bad a bit more, has this been turned up a notch?
5 Likes
CPU usage is higher for same amount of nodes right now compared to before the update. Bandwidht seems to be reduced 25% or so, memory also seems down similar %.
2 Likes
Seeing this too.
2 Likes
At least for me it is inconsistent, some have same CPU usage as before, one has higher CPU usage (AMD Ryzen), one has significantly lower CPU usage (Intel N4000).
2 Likes
@Erwin has been evangelising AMD and it’s performance when running nodes vs Intel. What see you Erwin?
1 Like
When I try to launch the new Launchpad I have the same problem as before the update, Manage Nodes indicates that: “Using 0GB of 1GB available space”, @chriso wrote that it will be possible to select the drive on which we want to run nodes, has this feature been implemented in the new Launchpad? What should be done to change the path?
No Safe, no wave.
I just dropped my node count vs Beta-One CPU is a killer for me.
2 Likes
I see much higher cpu usage. Same machines that ran 500 nodes without issues are now screaming and suffering and asking to be taken out the back to be shot in the head.
5 Likes
My first join attempt assumed lower base traffic meant I could add a few more 
2nd attempt with the same as before was still a nope.
3rd time is hopefully a charm with a reduction BUT what happens when the intended increase in uploads gets unleashed. I hope that I am conservative enough.
1 Like
@happybeing, @neo can i ask for some guidance?
I can’t advise. I gave up on launchpad because it wanted to limit me to 1 node, but with safenode-manager I’ve been running >20.
EDIT:
Uploads have restarted, though no nanos for me yet.
2 Likes
Thanks, I got a bit of a virus (weakened) recently and wasn’t up to date, but early on Chris wrote that the launch drive selection would be prioritized in changes, I thought this would be standard in Launchpad.
In that case I will also go back to Safenode manager …
I apologise, I thought the feature would be going in. I’m not actually working directly on the Launchpad myself, but I will see about getting this feature in for the next release.
This is not completely set in stone yet, but, up until launch, we should now be having a release every two or three weeks. I’m working on making the process run smooth.
Regarding what features are actually in the new Launchpad and other releases, I’d like to bring people’s attention to the Changelog: safe_network/CHANGELOG.md at main · maidsafe/safe_network · GitHub
This is going to be part of the new release process. Rather than the automatically generated changelogs, which quite frankly, were pretty useless, this one will be composed manually and is intended to be easily understood. So, you can see that not much was in the Launchpad release, but hopefully we will get more improvements in during the next cycle, including the ability to specify those locations.
3 Likes
Thanks to the work that Shu has done for us, we actually now have the ability to compare the previous release with the next release candidate. We done it as part of this cycle and I don’t believe we observed anything with excessive CPU usage as compared to the last version.
1 Like
My little SBC cannot run as many nodes due to CPU. (noted after 12+ hours)
Now is that increased uploading traffic?
Is it nodes just using more CPU?
Is it more churning in new network?
This is what makes it hard to be able to say
We are doing lots of different comparisons with lots of different metrics, across all the nodes we had running, and we done it over several days. We’ll do that as part of each release from now.
I’m not saying there isn’t anything wrong, just saying we didn’t observe anything out of the ordinary with respect to CPU.
4 Likes
Hi @Chris, are you able to discover the status of the upload bug I reported. Being worked on or not, believed fixed or not. I can’t see it in the commits but the commit messages aren’t much to go on. Thanks.
Ref to report including logs: Assemble at the Start Line. The Beta is About to Begin - #568 by happybeing
tl;dr: when uploading a directory it repeatedly drains the wallet, charging way more times the estimate for uploading. this bug occurs in both safe files upload of a directory and my app which uses the FilesApi to upload a directory. However, if you upload the same files individually, that works.