Update 17th October, 2024

Thanks for clarifying that!

1 Like

Can you please just go away. Your continual negativity whilst the solution is just about to be released is becoming tiresome.

Unless you can come out with certain substance that something is going tits up, I don’t see the point of you just repeating how unhappy you are.

8 Likes

Happybeing has been here forever and cares deeply for the fundamentals. You can’t tell him to go away. He’s rightly concerned as are many OGs.

He’s defended it when the community was overly critical. He’s defending it with his constructive criticism.

17 Likes

That’s a bit rich coming from you. you usually only pop in for a moan.

9 Likes

He’s getting some doe back soon :stuck_out_tongue_winking_eye:

3 Likes

My guess, yes guess at this stage, is that the partners are only going to start uploading after TGE (the genesis event) since its pointless to upload prior to TGE except for testing purposes.

I cannot answer. My personal thought is that after TGE it only makes sense for files you really want on the network and a smallish number of small files every so often. Before TGE, is there any good reason to spend gas fees on what essentially will be test files.

You get your chance during this coming week before 1st stage launch on the 29th to upload with fees covered

5 Likes

Could it be that @WeeBert did not enjoy his Killie pie this afternoon?

3 Likes

Deer, deer, I have no idea what you mean…
And thats me being hind err err kind…

2 Likes

I think it’s time we stop all the negativity and personal attacks. This forum has always been a place for constructive feedback and difficult discussions. I know @happybeing doesn’t shy away from those, and I appreciate him for it.

Now that there’s a timeline involved, things tend to get more heated, and that’s understandable. But take a moment to consider how this forum appears from an outsider’s perspective. We’re just weeks away from going live and attracting new people into our community. What standard are we setting for how we debate? How welcoming are we?

We all want this project to succeed, and we’re all on the same team. Can we return to treating each other with respect?

9 Likes

There’s a lot of confusion here and mostly caused by the absolute push by the team to get us something in our hands we can truly play with.

What many are failing to see, and my bad for not explaining it, is that the over provisioning of nodes is bad, but it’s possible in the tests. It does do harm in small population networks.

Here’s a quick brief on that topic.

  1. Nodes should have a certain disk space per node
  2. They store and serve data up to that size
  3. They should never got to 100% full, somewhere between 20 and 80% full (price elasticity etc.)

So folk are in the testnets running as many nodes as they possibly can to earn more and all that jazz. This is the awfully termed game theory, which I hate, but it’s folk trying to do more for whoever reason.

In the live network (and we need to get closer to a live network) then nodes will be mostly serving data.

Nodes that don’t serve data are shunned, so killed basically. This is not happening so much in the testnets as there are no apps and few downloads to catch bad nodes. This is a reason to push like mad to get a network up and running with an API and get app using it. It’s that balance of real life and ability to test. It’s a fine fine balance, we must get close to.

So in the real network folk will maybe try and overprovision. They may note nodes are all 50% full for instance and run 2X as many nodes as they should. So cool, if they are working we don’t care, it’s perfectly fine.

BUT if there is a sudden change in economics or network use (same thing) and nodes need to be 51% full then all those overprovisioned nodes will be killed. Operators will have to restart and that will cost them time and money to do so.

So basically the network can handle over provisioning, it’s perfectly cool, but operators take big risks in doing so and some of those risks will cost money.

So now we will get some supper smart operators front running this and provisioning just the right amount to get max profits and be able to dramatically alter space available to make Their nodes OK and providing just the right amount of space and so on.

Or folk will say, you know what, the network is stable as hell and I prefer not to worry about all the shennanagins.

Both types of operators is cool though, as long as they store and serve data (later implies the former).

In tests we have seem though massive node over provisioning and then >90% of the network being taken offline in one swoop. That’s helping nobody.

So there it is. This is why the team are asking for more care/reality in how we run these nodes. Overprovision like mad and supply insane % of the network and the tests junk.

Hope that helps.

17 Likes

I think it is important to note that the leaderboard introduces a motivation that will be absent in the live network.

Winning.
Nobody should underestimate the drive to overprovision due to the competitive nature of these tests.

11 Likes

Except these 32GB node / 4MB max chunk never got above 1 to 2GB in storage so that issue of disk space in those networks didn’t occur.

CPU usage due to the retries was an issue.

I am doing a write up that discusses router (ISP supplied) RAM size and chunk size are extremely important and found a (proper) fix to solve that issue for 4MB chunks

12 Likes

I have a device with 850GB free space and reasonable RAM and CPU. The Launchpad tells me I can run 24 nodes. How many nodes can I actually run before I run foul of over provisioning?

3 Likes

What launchpad told you. It’ll be approx 750GB / 35GB

750GB because you should always leave some unused space on a drive

2 Likes

…so 21 then!

2 Likes

I’d recommend adding more gradually and monitoring CPU and mem usage as you go.

Other things to consider are available bandwidth and what router can handle connections wise.

Again, ramping up gradually monitoring as you go (espeically if you intend to try and run that many) is the best strategy

6 Likes

Plus, in recent tests, it turned out that at times of load, you need 20 Mbit upload speed per node, at least according to what is written in Discord. Can the team confirm this, Jim?


Check out the Dev Forum

1 Like

That need isn’t supported by my observations. And there is a setting in QUIC that solves the issue anyhow

5 Likes

The forum positivity and negativity are in perfect balance. Just the right amount of cheerleaders, mixed with the perfect blend of critics. :balance_scale:

One thing about deadlines, they add a lot of stress. So the community is more stressed than usual as the deadline approaches. :tired_face:

People worry about the deadline instead of the project itself. Having focus is important.

9 Likes

got to love harmonics, not.