SAFE Network - TEST 6

There certainly does seem to be a lot of great progress in these tests.

I’d also be interested in hearing thoughts of devs on the performance so far.

Is performance in line with expectations, and is there a clear path to increase performance once the basic network is refined?

As I understand it, once the network is big enough, users should be able to download many chunks in parallel, so even if the speed per chunk is slow, downloading large files should be fast.

Do we just need a bigger network to see this speed, or is there something else constraining performance at this early stage?

Edit: just seen Pierce’s new thread - feel free to move / delete this if appropriate mods :slight_smile:

As a rather none expert Dev I’d say it is hard to say much about performance based on the testnets from outside MaidSafe.

Because we don’t know in detail what the tests are trying to achieve and how representative they are, what tweaks have been made to be taken out, what known issues plan to be removed etc.

I think when we reach alpha that will give us a baseline which may well be improved upon, but something we should take as a good indication of early performance characteristics. It will be potentially very different when the network scales though, so even at alpha, still only a guide!

5 Likes

a bit of churn coming up right now as I have to reboot my pc as the demo app wont connect to the launcher and that same pc is running one vault of 200mb and also has a terminal window open to an azure vault with another 200mb, both been running about 15 hours…

After a reboot of my windows pc still the demo app is not getting its authorisation after I hit “Allow”

Demo app says waiting for response but launcher thinks its in progress.

Anyone else with issues this morning?

Cheers
Al

1 Like

got some msg’s

off out for the day, it is sunny in London

enjoy
cheers
Al

I tried to do exactly the same thing and got exactly the same result. It seems like big files (e.g 46MB) get stuck. Error messages are mixed too with the demo_app saying stuck on 99% but with the launcher saying success.

On restarting the demo app the file appears in the demo app private files folder, but downloading and trying to open it in the archive manager doesn’t work so it’s obviously incomplete.

1 Like

“Will you walk into my parlor?” said the fly to the spider:

http://her.again.safenet

I tried uploading 1.7GB of folders containing ~100mb worth of mp3s each. The demo app had been stuck on 0% for around 2 hours, though it does show 9.4MB uploaded. Upon restarting everything, I had apparently gone up to 11/500 PUTS. I can see folders in my private data but no files. I can post logs if requested.

2 Likes

vault stopped about 3 hours ago. just restarted it.

INFO 05:30:02.651724491 [routing::core core.rs:390] | Node(1254ca…) PeerId(08da…) - Routing Table size: 16 |
INFO 05:30:02.651738562 [routing::core core.rs:391] ---------------------------------------------------------
INFO 05:30:02.651770108 [routing::core core.rs:2304] Node(1254ca…) Dropped 1453e7… from the routing table.
INFO 05:30:02.651827618 [routing::core core.rs:2304] Node(1254ca…) Dropped 174fb5… from the routing table.
INFO 05:30:02.651891521 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(54b0…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.651926715 [routing::core core.rs:2304] Node(1254ca…) Dropped 151b20… from the routing table.
INFO 05:30:02.651959078 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(c5da…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652000213 [routing::core core.rs:2304] Node(1254ca…) Dropped 12afce… from the routing table.
INFO 05:30:02.652029652 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(7b80…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652069053 [routing::core core.rs:2304] Node(1254ca…) Dropped 1ff4b7… from the routing table.
INFO 05:30:02.652103527 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(efe6…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652142333 [routing::core core.rs:2304] Node(1254ca…) Dropped 0656f7… from the routing table.
INFO 05:30:02.652167825 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(159c…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652206771 [routing::core core.rs:2304] Node(1254ca…) Dropped 01b700… from the routing table.
INFO 05:30:02.652235974 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(792b…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652274570 [routing::core core.rs:2304] Node(1254ca…) Dropped 37a929… from the routing table.
INFO 05:30:02.652301586 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(c685…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652330610 [routing::core core.rs:2304] Node(1254ca…) Dropped 31e47a… from the routing table.
INFO 05:30:02.652386769 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(3d87…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652427971 [routing::core core.rs:2304] Node(1254ca…) Dropped 3ca51d… from the routing table.
INFO 05:30:02.652468072 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(8291…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652502064 [routing::core core.rs:2304] Node(1254ca…) Dropped 26d1a2… from the routing table.
INFO 05:30:02.652542118 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(e1f3…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652577698 [routing::core core.rs:2304] Node(1254ca…) Dropped 41e236… from the routing table.
INFO 05:30:02.652619342 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(f4a0…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652653545 [routing::core core.rs:2304] Node(1254ca…) Dropped 9ba078… from the routing table.
INFO 05:30:02.652693549 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(b0b4…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652726461 [routing::core core.rs:2304] Node(1254ca…) Dropped 90a91a… from the routing table.
INFO 05:30:02.652765458 [routing::core core.rs:1139] Node(1254ca…) Connection to PeerId(84d1…) failed. Calling crust::Service::disconnect.
INFO 05:30:02.652799329 [routing::core core.rs:2304] Node(1254ca…) Dropped 827148… from the routing table.
INFO 05:30:02.653321058 [routing::core core.rs:373] Node(1254ca…) - Indirect connections: 0, tunneling for: 0
INFO 05:30:02.653362797 [routing::core core.rs:388] ---------------------------------------------------------
INFO 05:30:02.653384567 [routing::core core.rs:390] | Node(1254ca…) PeerId(08da…) - Routing Table size: 1 |
INFO 05:30:02.653407697 [routing::core core.rs:391] ---------------------------------------------------------
INFO 05:30:02.656062294 [routing::core core.rs:2304] Node(1254ca…) Dropped 1e1f49… from the routing table.
INFO 05:30:02.656111460 [routing::core core.rs:388] ---------------------------------------------------------
INFO 05:30:02.656128876 [routing::core core.rs:390] | Node(1254ca…) PeerId(08da…) - Routing Table size: 0 |
INFO 05:30:02.656146783 [routing::core core.rs:391] ---------------------------------------------------------
WARN 05:30:02.849500139 [safe_vault::vault vault.rs:188] Restarting Vault

I am commenting as user (investor), I am not a developer or programmer.

The performance is a but slow, I would say very slow, but it will improve, I am sure.

Visited several .safenet sites and it took at least a minute for the sample sites to load up.
Uploaded a 47MB file, according the launcher it was successful, but the app just stuck on 99% then I closed it down after 30 mins waiting.

Otherwise so far so good.

2 Likes

for me the current testnet-iteration works very slow too. - I also got problems when uploading files (like the ones described above).

For those who missed this reply:

11 Likes

Hmm. Something not quite right here. I upload a PDF file size 1,626,778 bytes. When I download the file it is only 1,572,864 bytes (and not surprisingly will not open).

2 Likes

Demo app is not connecting here.

Loving the new client. Im sure the new week will see these wrinkles ironed out.

5 Likes

i too am having troubles getting demo app connected, also a lot of hanging at 99% when uploading files. I want to upload as much as possible to stress the network but wish i could get these larger files uploaded

2 Likes

Hm, my private folder still seems to be broken. Fails to fetch directory and it’s not possible to upload files anymore. Would be very interesting to know how a canceled file upload can break the whole folder. (PUTs to the public folder still work) Maybe one of the devs could shed some light onto this.

1 Like

I’ve had some success… uploaded 43 items (28.7MB) without issue - checked with sha256sum that the download matched ok. So, then I tried x8 files roughly 23MB each and I see now it stuck at 13% for the last 40mins… log detail in GUI suggests success on each element… but it’s just not obviously trying the next step - which I expect is the next file, given limited detail I can see of the uploaded amount relative to being two files size.

I guess it’s to be expected there will be problems like this, if no messaging priority is in place and perhaps limited capability to respond where no reply is received to requests… compounded with perhaps weakest vault influencing performance… which I keep wondering is mine… would be great to see an indicator or message from the vault suggesting it’s relative capability and that is was being useful.

Perhaps when messaging priority is enabled, vaults could declare the volume in each flavour of message that could then be interpreted as an indicator of it’s performance and capability relative to others - or some normal.

3 Likes

Windows 10.

I can´t get the Demo app to get authorized by the Launcher.
It is stuck in “Waiting for response” although I have granted it access in the Launcher. In the Launcher Logs Status it just says “IN PROGRESS”. I have tried several times now, and I can´t access the demo app.

Running
Vault 10.4
Launcher 0.6.0
Demo App 0.4.0

Create a new account.

1 Like