Just sometimes off by a little while ![]()
I’m hoping v6 has pique performance…
![]()
The new post symbol peaked my interest too!
Excuse the innuendo! ![]()
Can we keep this on-topique please?
Spelling is just one element of intelligence. In fact, smart minds often don’t even see the mistakes, as your brain fixes them without you realising.
That said, it often surprises me how much code has typos in it. I’ve even seen entire abstractions use a bad spelling and often no one is brave enough to fix it! ![]()
I can tell you’re a good dad Jim ![]()
Dad jokes ftw
I don’t think spelling has all that much to do with intelligence. But the ability to focus is important, and that’s not really encouraged these days.
I love spellcheckers, and I’ve actually worked on developing some of the ones Microsoft integrates with its products.
Spelling is just one element of intelligence.
Yes, of course . . my inability to pick up languages or musical instruments as easily as some people is annoying - not to mention Emotional Intelligence etc etc . . I guess there is an argument to be made that obsessively correcting spelling and English errors that will not make any difference anyway shows a distinct lack of intelligence . .
mount/umount command springs to mind.
Is that pique gique?
Spelling is just one element of intelligence. In fact, smart minds often don’t even see the mistakes, as your brain fixes them without you realising.
I recently listened to an interview with Michio Kaku and he said that all high IQ proved is that one was good at clerical work. Those that are messy often have lower IQ’s but greater creativity and survival skills.
IMO, the world needs both and working together. They have their own strengths and weaknesses.
Here we go, V6 today! Come on! ![]()
What do you think language sounded like 50 years ago, 100, 1000 years ago?
I’ve read some Shakespeare, sometimes degradation is a good thing.
That sounds to my ears like a pretty mashed up blend of English, Danish, Norwegian (I speak English and Swedish) and German.
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.
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?
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.
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 |
nodes behind NAT (igd) that is failed
Best bad news I’ve heard in a while, thought I was doing something wrong ![]()