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:46.101.49.165 ttl:300
A name:nuseed.coinerella.comaddress:5.135.184.184 ttl:300
A name:nuseed.coinerella.comaddress:96.46.29.134 ttl:300
A name:nuseed.coinerella.comaddress:79.165.45.95 ttl:300
A name:nuseed.coinerella.comaddress:94.23.252.118 ttl:300
A name:nuseed.coinerella.comaddress:74.71.28.67 ttl:300
A name:nuseed.coinerella.comaddress:91.220.43.146 ttl:300
A name:nuseed.coinerella.comaddress:81.169.207.53 ttl:300
A name:nuseed.coinerella.comaddress:85.214.145.24 ttl:300
A name:nuseed.coinerella.comaddress:62.75.163.12 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.
I’ve been working with sigmike the past two days on trying to resolve it. He’s looking at the code. It seems to be mostly a windows issue which helps narrow things down a bit. From there I’ll try to get some more RC builds posted for the community to help test. If we get good feedback we can probably cut the release build after that.
Just found another bug in v2.1 RC8-beta (which you shouldn’t really use) with the parking.
Although the parking amount shows up in the overview screen, the actual park transaction doesn’t show in the ‘Park’ window. Unfortunately the funds have been parked till 2 November, so it will be a while to find out whether the transaction still worked and that it is only a display/gui issue. @sigmike
In v2.01/v2.03 the parking works as it should. Tested that recently.
Thanks @Cybnate for helping us move this a little closer to release. It would be great to see the optimization release actively developed again. @sigmike what are the prospects you will facilitate that?