Pre-Dev-Update Thread! Yay! :D

That sounds to my ears like a pretty mashed up blend of English, Danish, Norwegian (I speak English and Swedish) and German.

2 Likes

They regressed from that to Estuary English? Or worse, received pronounciation…

That’s brilliant! As the guy says in the description, it’s not really correct, but I think it’s a great way of presenting the subject.

1 Like

Quick update today - we’ve been fighting against a few last minute issues which are holding us back from releasing a testnet today.

Would you mind linking to these specific issues, if they’re on Github?

1 Like

They are not on gh it’s running nodes behind NAT (igd) that is failed, not our crate, but seems a failure there. So investigating now with lots of us trying from lots of locations. It’s a PITA simple plain network issue, nothing worrying but a PITA for certain.

20 Likes

Is there any point in contiuing with profiling the sn_node performance?
These figures need to be taken with a huge pinch of salt anyway - its only one run on one machine.
If you feel there is any value then I would run the smaller tests say 5 times each and take an average.

filesize sn_node 0.48.1 sn_node 0.49.0 sn_node 0.49.2 sn_node 0.49.7
5MB 2m1.468s 0m14.686s 0m14.785s 0m18.793s
10MB 3m43.119s 0m35.215s 0m36.218s 0m45.235s
20MB 6m59.187s 1m29.119s 1m39.737s 1m51.249s
50MB 17m25.503s 5m40.328s 5m48.750s 6m39.017s
100MB 41m34.945s 15m53.138s 16m27.564s 21m20.357s
200MB 110m25.682s 61m19.929s 73m21.797s 73m17.555s
512MB 368m8.248s aborted 388m26.748s aborted
7 Likes

Best bad news I’ve heard in a while, thought I was doing something wrong :grin:

9 Likes

Quick @Josh call it for tomorrow :wink:

3 Likes

You are a bad man, @scottefc86, a very bad man indeed :grin:

2 Likes

PITTA . . .

2 Likes

It’s just a Liverpudlian thing, or is Mancunian?
Not sure thers is a big difference :crazy_face:

2 Likes

Careful or you will be a candidate for either a good kicking or remedial spelling lessons

3 Likes

Probably both.

3 Likes

NAT issues have caused so many bloody noses over the years for SAFE. Part of me wants to just bale on the whole thing and force node operators to learn how to forward a bloody port, just like so many other projects do. This would mean some sort of onboarding script that picks a random number, writes it into the config file, and then tells the user to open that port in their router, so we could still have unpredictable ports.

8 Likes

or use ipv6? just learned it doesnt have NAT

3 Likes

I’m still scared of IPV6. I now always disable it in my routers, after reading how so many devices have IPV6 vulnerabilities. I have a lot of random junk on my network, and don’t want to worry about what vulnerability each thing has.

4 Likes

Yikes! How big an issue is it?

But sounds like everything else is on track. Team flying high :airplane::airplane::+1::+1: keep it going :blush:

4 Likes

Coming from you I’ll take that as a compliment :joy:

6 Likes

What are IPV6 vulnerabilities, can you explain in short why?
So tired of the IPV4 shortage of addresses an IP’s CGNAT.

My money is still on next week. And next week, I may have to cover that with money on the week after. But coming soon

1 Like