I have 2 machines that have ran from the start have never gone above 60% another 2 that creep to about 80% but sometimes higher and have to restart. One of those is using home network so could be that. Only other difference between them is the location and internet speed 
I don’t use home-network but find it can just about double in a couple of days of running and then yes it will fluctuate as Neo says.
Thats what mine do. Its about double the cpu usage after 24-48 hours than at the 1 hour mark
1 Like
Sorry, I’ve been off sick the last week.
There’s been a lot of work on processes etc at the moment. Trying to get release flows and testnets stable so we can properly vet things before going out to the community.
As well as debugging of issue we can now see more clearly with monitoring (there was some hiiigh bandwidth eg).
Essentially, we’re trying to test/verify before we get new nodes out to the community. So it’s a bit slower, but worth the investment in the flows here, I feel.
10 Likes
The autonomi news said a couple days ago that Monday 2pm (UTC+1) the new network will be setup ready for the new programs to be downloaded and connected to.
Are you saying there are more delay to that time?
I’m not saying anything beyond what I said above 
Just trying to highlight why things might feel slower for some folk.
1 Like
I was asking because that time is like 11pm for me so its a matter of deciding to stay up of not
But no problems, I’ll wait like everyone else has to do
5 Likes
Good to hear from you Josh, hope you are fully recovered and it was possible for you to get the rest you needed. Take care man. 
Oh, and fix my upload bug pronto 
8 Likes
We have a 24h window no? Do you think there is reason to stay up.
2 Likes
Look we know this, but how can I miss the start of the new network
7 Likes
priorities 
4 Likes
Looks like the release is in process. 
3 Likes
Patience glasshopper, it’s a process. 
At least that’s what I assume!
2 Likes
Im very patient, planning on waiting a little while to see how you all get on. 
4 Likes
I already have awe built and tested against this release using a compatible local network so all I need is a working 
public beta network and… tokens.
EDIT: seems to have gone quiet on github
8 Likes
4 Likes
I’m hoping this will reduce the problems with nano transfers and paying for chunks that I’ve been seeing. 
Unfortunately there is no information about what it is trying to address, and links the github issue to a private Slack discussion. 
Any chance of a short summary @joshuef? I asked a couple of weeks ago but didn’t get a response.
5 Likes
That work is reducing the code for spends, and opening the door to other improvements around spends.
Reducing complexity across the board. It’s not necessarily going to fix the issue you’ve been seeing, but should make debugging it easier 
11 Likes