I’m stumped.
I get the same results using my pc/laptop/cross.
1 Like
You are still getting huge binaries on both your PC and laptop, using both cargo and cross. ???
I used cross maybe 2-3 times building for Pi ages ago and its not on this new box. yet
FWIW I have rustc 1.60.0-nightly (777bb86bc 2022-01-20)
Ahh I see a misunderstanding.
That is the amount of memory they are using when they run.
Yes same result from either way laptop/pc/cross
1 Like
I get the same result as you do using my compiled sn_node with baby-fleming. different story on DO.
1 Like
However when I actually give that network something to do, its a different story
willie@gagarin:~$ du -hs ~/Pictures/2008
534M /home/willie/Pictures/2008
willie@gagarin:~/.safe/node$ safe files put -r ~/Pictures/2008
The answer seems to be your Maidsafe binaries were under load, your homebuilt ones were idling.
Not really the results are directly after starting a network on DO so exactly the same situation for Maidsafe vs home built time and time again.
need to pack it up for the evening though, thanks for jumping in @Southside
1 Like
Need to be absolutely certain we are comparing apples with apples here.
How long after the first node is initialised are you taking these figures?
How many nodes are in each network?
1 Like
Always immediately after launching a network and before using it in any form whatsoever.
1 Like
What about after a certain amount of work is done?
Heres my processes after ~500MB has been stored
://5nbJUqpyoax1ArriM7t80aC81lZ.png)
Adults use much more memory than Elders is all I can reliably tell from that.
I’'ll try to come back in a while and compare, get exact numbers (if not in the morning)
But from past experience Maidsafe’s perform better under load too.
Probably going to smack myself when this gets figured out!
2 Likes
Are you compiling with musl?
cargo build --release --target x86_64-unknown-linux-musl
11 Likes
Could it be that Maidsafe binaries are compiled on DO and run on DO, yours are compiled at home and run on DO metal - is that correct?
1 Like
I’m off to compile with the --target x86_64-unknown-linux-musl parameter and see if I notice any change.
1 Like
No, I’ll give that a go shortly.
wee bit prep may be needed…
Compiling fnv v1.0.7
Compiling futures-sink v0.3.19
error[E0463]: can't find crate for `core`
|
= note: the `x86_64-unknown-linux-musl` target may not be installed
= help: consider downloading the target with `rustup target add x86_64-unknown-linux-musl`
= help: consider building the standard library from source with `cargo build -Zbuild-std`
1 Like
Solved, thank you @mav!
12 Likes
@maidsafe, are you possibly planning to make this kind of playground a regular thing? It seems to me that this one did not require that much involvement from your stuff, but what do you think? I think these could very well be kind of self directed play for the community.
I am asking, since it seems to me, that barring this Playground and recent Comnets, the community is not very vital at the moment. Even the participation in these testing opportunities has been a bit lower than I expected. That’s based on the threads here, of course there could be people participating silently.
Anyway, even if it would not be essential from the perspective of development, I think it would be good to have regular Playgrounds for the liveliness of our community. To make them regular would mean we have something to expect - and prepare for. And to make them a bit more directed, would in my opinion help to grow the enthusiasm. By “directed” I mean knowing what aspect we are playing now, like for example “Now we play splitting with 3GB nodes.”
8 Likes
Aye that’s the hope!
Honestly there’d have been more recently, but we’ve made a bunch of changes to the release process and pr merges the last weeks that have thrown some spanners about.
I’d actually quite like to see if we can repro missing chunks (i’ve failed to repro that, but we’ve also seen a contender bug for this, so will be good to know!) so it might be a super stable 20gb next. But 3gb not far after!
8 Likes
I thought tiny vaults(3Gb) was our next priority to facilitate new nodes joining and give us more chance of section splits?
4 Likes