dunno - still compiling it on my RaPI2
I was close to proposing one of you might create an issue for it, but it appears that bug is already known:
Sorry for crying wolf…
…but like I said: it’s a release candidate and not the release!
edit: impressive - nud starts very fast on the RaspberryPi and consumes only little RAM (as little as 38 MB):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27552 pi 20 0 223m 37m 8028 S 1.3 3.8 0:03.88 nud
Unfortunately nud doesn’t connect to peers. I killed nud, deleted addr.dat and peers.dat hoping that would solve the problem and started nud again without avail in terms of getting connected to other nodes:
It is true that the latest 2.1 build is accessible in the public code repository. However, it is not yet of the quality needed for even a limited beta release. There are a number of significant problems that need to be resolved at this point. I recommend it not be used yet, except for testing.
On one machine, the latest 2.1 build showed a 65% reduction in RAM utilisation and a 94% decrease in the time required to start the client. Your results may vary, but 2.1 certainly includes major performance enhancements.
Note that there are major internal changes in this release and you should backup your datadir before upgrading. The whole block index will be rewritten during the first startup and this may take some time. I’m not sure you can run the 2.0 client on the rewritten index.
A name:nuseed.coinerella.comaddress:184.108.40.206 ttl:300
A name:nuseed.coinerella.comaddress:220.127.116.11 ttl:300
A name:nuseed.coinerella.comaddress:18.104.22.168 ttl:300
A name:nuseed.coinerella.comaddress:22.214.171.124 ttl:300
A name:nuseed.coinerella.comaddress:126.96.36.199 ttl:300
A name:nuseed.coinerella.comaddress:188.8.131.52 ttl:300
A name:nuseed.coinerella.comaddress:184.108.40.206 ttl:300
A name:nuseed.coinerella.comaddress:220.127.116.11 ttl:300
A name:nuseed.coinerella.comaddress:18.104.22.168 ttl:300
A name:nuseed.coinerella.comaddress:22.214.171.124 ttl:300
Any update on this? I’ve been encountering some issues with my 2.0 client (long loading times, lots of orphans, blockchain download freezing, etc…) It may be because I’m running everything on an older and slower computer. I figured maybe the new version might fix my problems, since it’s supposed to use less resources.