Developeres mentioned that they think that the network without sharding will be able to pull 8-10k nodes.
As far as I can see, the production of blocks was going fairly well.
On the link below you can see the last blocks of the epoch 51. It shows the validation was progressing and how the network worked.
https://scan.idena.io/epoch/51#blocksOnly hickup that I saw was this:
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FClU07s2.png&t=665&c=5xgdiwH_ElImRA)
At that point in long session, network formed committee of nodes that were problematic, probbably low hardware resources, hogged ram or low powered cpu that were not able to produce 3 blocks.
Before that we see around 150 transactions per block. After that network got to a node with good hardware, and it produced block with 588 transactions.
VPS's with 1GB of ram are barely making it through. If you restart your node on VPS, you will clear it's hogged memory and it will perform perfect. But if you let it run for 10 days or so without restart, it will hog up ram memory, continue to use swap(virtual memory) and will start performing slowly and even posibbly go out of sync.
https://github.com/idena-network/idena-go/issues/514Some optimisations if possible regarding this are needed if we want to stay in the 1GB ram requirements.
Judging by the block sizes during validation, we had that block with 588tx that was near 230KB. Block max is 300KB currently.
Untill we start seeing more of these bigger blocks we are not nearing network maximum.
We saw a growth of +300 in number and it came with good news and price increase, which is great. I'm sure we would have more validated identities if new people could understand that they can't sync their node few hours before validation, from VPS, they probably can, but from home enviroment, higly unlikely.
Other problem that is happening in high number is so called "Late subbmision" where you do the validation and submit on time, but something is not right and your answers are not submitted on time for short session. I have never experienced this during my validations. So it's not random bug, I think that it happens in two cases:
1. You run node+client in home enviroment and have poor connection/router that causes node to go out of sync, even if your client does not show you these small time periods when your node is not in sync. Or your local PC time is not synced, check on
www.time.is2. You run node at 1GB VPS but you have not restarted it for a long time, ram hogged, node out of sync. Also if node is ok and your time at local pc is out of sync, that can also be an isuue.
So, now, we have:
- "Late sync" people (wasted invites)
- "I forgot" people (killed newbies)
- "Late subbmision" people (bug)
Make sure you have decent hardware. If you run your node at home, run it with lowpower and profile=server. Make sure you restart node, 1 day before validation if you run on 1GB vps. Make sure your time is synced.
Video that shows how to run node on windows with lowpower and profile=server options that will cause your node to make less connections and put less strain on your probable low-end home router.
https://www.youtube.com/watch?v=bQ2qi8MbR3I