Further Improved Synchronization Test
administrators

I made some nodes filtering and changes to bootstrap nodes loading and its active in the current nightly builds at: https://builder.musicoin.org
This is why I ask community to test synchronization speed and peer connectivity between current 1.0 and last build we have currently available.

To test it you need to download build for your platform at: https://builder.musicoin.org, launch your wallet and select Advanced - Wipe blockchain. After you need to follow the instruction (confirm wipe and restart the wallet).
Do sync from the 0 to 100% and save number of peers and time it took. After you need to wipe again, close the wallet. And sync from 0 to 100%, but with release 1.0 from GitHub.
Write your location, number of peers and time from 0 to 100% sync with nightly version and 1.0 in the comments.
Its expected that in case you already have good synchronization you should see a change only in the connectivity (number of nodes you connected too).
But those changes was made for people with bad connectivity.

last edited by cryptofuture

Thx for your hardwork !

Testing it… its stucks almost 40 min at 99.96% (took 10min to get to 99.96 block 500000 something). I assume its writing data to the disk?
Jumped back to 24% then and now its doing a slow sync…
I coudnt wipe the chaindata via the menu… didnt start as an admin
I wiped it manually
The search for nods seems to be faster, i was connected to 8 nodes before it jumped back and i canceld it

last edited by MJMoonbow aka Tinman

Im giving it anothe try this morning and renamed my whole mc folder in %appdata%
This time it chooe block 1600000 as top block and jumped back to slow syncing after reaching it
I cancel now at 83% 50 min
Deleted the whole folder again and started 1.0 wallet
it choose 1.86 million as top block first and did fast sync only 4 peers
after junping back % its now at 90,4% sync in 40 min
So nightlybuild seem to connect better but 1.0 is faster with sync…

last edited by MJMoonbow aka Tinman
administrators

@MJMoonbow-aka-Tinman That is interesting data. I think I might need to clear nodes list completely, and start filtering only fresh discovered nodes. Try to repeat test with nightly version tomorrow, should be enough time to collect more nodes from the start.

Basically the difference between version is in 0.7 bootstrap didn’t worked at all and full sync was used.
In 1.0 fast sync is used and big list of nodes preloaded, and also you saving locally discovered nodes at the top of the list and it works quite good if you have normal connectivity by yourself, so at the start of the wallet you could connect to the new discovered nodes fast. But problem was is that for some reason people discovering fast bad nodes and trying to connect to them.
And in the nightly bootstrap list is loaded from the GitHub repository (where list is filtered and auto-updated) and local list is used only if you can’t connect of the GitHub. But con here is that nodes from that list might not the be fastest from the your location, but at least we know that those nodes are online. So you connecting to more nodes (better connectivity) but nodes you start with, are not always best for your location.
You should be able to delete gmc folder from the menu, our access to the %appdata% limited by admin in the office policy for you? Basically typically all programs in the Windows run under admin account.
Provide logs, from the moment when you confirm wipe. Advanced - Open logs folder

Chaindata were on usb drive via symlink. Im gonna try the blockchain wipe with new nightly build tommorw 🙂 not sure if i found it lol need to delete the logs before trying…
[03-01|19:46:29] Skipping deep transaction reorg depth=2048

Uncaught Exception…SyntaxError: Unexpected string in JSON at position 83740
SyntaxError: Unexpected string in JSON at position 83740
at JSON.parse (<anonymous>)
at HTMLElement.activePeers (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/elements/msc-profile-view/msc-profile-view.js:356:26)
at chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/elements/msc-profile-view/msc-profile-view.js:1043:50
Musicoin Wallet stderr: INFO [03-01|19:46:37] Imported new chain segment

Maybe you could group peers to colums europe, asia, america and ping wich group is the fastest and choose the nodes from this group first.

administrators

@MJMoonbow-aka-Tinman Delete would not work with symlink. You should use move data dir in nightly version instead. Also usually usb sticks are slow, and you writing data in the cache first, so if you let’s say would close and restart a wallet fast, while data would still be written from cache to usb stick, you could easily lose last data on the stick. Which is means you could lose some blocks or could even break all chaindata to the state it couldn’t be checked. Or you if was using USB HDD, those ones are more safe to use surely. But stick, don’t even think about writing something continuously on the stick.
Also seems local bootnodes files are spoiled on your side, and I recommend you to remove bootnodes.json and bootnodes.json.org from your %appdata% folder.
But anyway its better to test sync tomorrow, as I done reset for bootnodes.json and its really small now.

Yeah its a hdd via usb 3.0 so its fast enough and i dont unplug it… but for the test im gonna use my primary sdd…i just rename my symlink so it will create a new Musicoin folder in %appdata%
Gonna delete the bootnodes.json thanks for the hint
@cryptofuture

@cryptofuture
start 7:57
topblock 1,86
2peers after 5min
3-4peers 10 min (it was up to 5 inbetween) sync @ block 820k
5peers 15min sync @1,08 (just noticed top block is @ 2,07 not sure when it happened)
5peers 20min (dropped to 3 inbetween) sync @1,3
4peers 25min sync @1,6
6peers 30 min sync @1,8
7-8peers @ 8:31 100%sync
WOW full syn in 34 min!

administrators

@mjmoonbow-aka-tinman said in Further Improved Synchronization Test:

@cryptofuture
start 7:57
topblock 1,86
2peers after 5min
3-4peers 10 min (it was up to 5 inbetween) sync @ block 820k
5peers 15min sync @1,08 (just noticed top block is @ 2,07 not sure when it happened)
5peers 20min (dropped to 3 inbetween) sync @1,3
4peers 25min sync @1,6
6peers 30 min sync @1,8
7-8peers @ 8:31 100%sync
WOW full syn in 34 min!

That is totally OK, I do slower myself (on my connection). Also yesterday I filtered more than 100 bad nodes from the bootstrap file. Probably in the next gmc version bad nodes would be blocked by gmc itself.

ver 5.march @cryptofuture
1744
start with top block 1,649 (I think thats the block when i created the wallet adress i imported!!! So it starts to slow sync after hitting it.)
5min 3peers sync@ 84,000 blocks
10min 6peers sync@ 826k
15min 7peers sync@ 1,01 million
20min 7peers sync@ 1,35
25min 2peers dropped peers after hitting the initial top block not syncing

Synchronisation failed, dropping peer peer=d113dcd588599069 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: WARN [03-07|14:08:45] Ancestor below allowance peer=3add16e18bd55da6 number=1559581 hash=000000…000000 allowance=1559581
WARN [03-07|14:08:45] Synchronisation failed, dropping peer peer=3add16e18bd55da6 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: WARN [03-07|14:09:06] Ancestor below allowance peer=8ae417d97007ac43 number=1559581 hash=000000…000000 allowance=1559581

Musicoin Wallet stderr: WARN [03-07|14:09:06] Synchronisation failed, dropping peer peer=8ae417d97007ac43 err=“retrieved ancestor is invalid”

cancled and start over with creating new account

1421 just clicked on "open my wallet"
yes it starts with 2,097 as initial top block
5min 6peers sync@ 200k
10min 6peer 665k
18min 9peers 1,3 million
25min 10peers 1,74
dropped to 0 peers
30 min 1peer 1,8
35min 2peers 2,05
37min 2peers full synced
Tried to import account seem to have no effect
Tried to restart and imported again and it worked this time…

ver 8.3.2013
start 913
5min 2peers @24k
12 min 5 peers @600k
20 min 8 peers 1.1m
27 min 6 peers 1.4m
30 min 8 peers 1.6m
35 min 9 peers 1.8m
40 min 11 peers 1.9m
44 min 10 peers full synced
wiping chaindata:
Wallet stderr: INFO [03-09|10:01:41] Imported new chain segment blocks=1 txs=2 mgas=0.042 elapsed=11.029ms mgasps=3.808 number=2108587 hash=d20b53…a3ea60

Musicoin Wallet stderr: INFO [03-09|10:01:53] Imported new chain segment blocks=1 txs=5 mgas=0.116 elapsed=13.033ms mgasps=8.886 number=2108588 hash=89a12f…11ca09

Musicoin Wallet stderr: INFO [03-09|10:02:02] Imported new chain segment blocks=1 txs=1 mgas=0.052 elapsed=6.016ms mgasps=8.639 number=2108589 hash=c2b9cd…8cd5e9

Uncaught Exception…ReferenceError: gmcPid is not defined
ReferenceError: gmcPid is not defined
at HTMLElement.wipeBlockChainDataAction (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/elements/msc-profile-view/msc-profile-view.js:116:49)
at HTMLElement.handler (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:507:17)
at HTMLElement.fire (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:1295:6)
at Object.fire (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:867:23)
at Object.forward (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:1164:10)
at Object.click (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:1149:6)
at HTMLElement.handleNative (chrome-extension://iakcmlebjlcchobefajeefoajejdaikg/interface/bower_components/polymer/polymer.html:757:8)
Musicoin Wallet stderr: INFO [03-09|10:02:19] Imported new chain segment blocks=1 txs=3 mgas=0.063 elapsed=8.047ms mgasps=7.829 number=2108590 hash=b2d6c8…97ce3f

Musicoin Wallet stderr: INFO [03-09|10:02:34] Imported new chain segment blocks=1 txs=3 mgas=0.156 elapsed=17.046ms mgasps=9.148 number=2108591 hash=aea903…164158
@cryptofuture

ver 23.4.2018 windows-x64 on win 10
1223 wallet start
1226 wallet sync start
1248 @block 1,67 million to 9peers
1303 synced connectec to 10 peers
suddenly dropped all peers after full sync
[0_1522235353104_background.log](Uploading 100%)

@cryptofuture
Wallet stderr: INFO [03-28|13:02:11] Imported new state entries count=768 elapsed=2.005ms processed=968831 pending=1102 retry=2 duplicate=0 unexpected=0

Musicoin Wallet stderr: INFO [03-28|13:02:14] Imported new state entries count=768 elapsed=2.999ms processed=969599 pending=937 retry=2 duplicate=0 unexpected=0

Musicoin Wallet stderr: INFO [03-28|13:02:14] Imported new state entries count=649 elapsed=2.005ms processed=970248 pending=647 retry=0 duplicate=0 unexpected=0

Musicoin Wallet stderr: INFO [03-28|13:02:14] Imported new state entries count=359 elapsed=14.037ms processed=970607 pending=0 retry=0 duplicate=0 unexpected=0

Musicoin Wallet stderr: INFO [03-28|13:02:14] Imported new block receipts count=1 elapsed=0s bytes=17325 number=2223702 hash=40ae1e…e55b83 ignored=0

Musicoin Wallet stderr: INFO [03-28|13:02:14] Committed new head block number=2223702 hash=40ae1e…e55b83

Musicoin Wallet stderr: INFO [03-28|13:02:18] Fast sync complete, auto disabling

Musicoin Wallet stderr: INFO [03-28|13:02:21] Imported new chain segment blocks=134 txs=1572 mgas=60.313 elapsed=6.435s mgasps=9.372 number=2223836 hash=22c635…87ecea

Musicoin Wallet stderr: INFO [03-28|13:03:29] Upgrading chain index type=bloombits percentage=0

Musicoin Wallet stderr: WARN [03-28|13:03:29] Synchronisation failed, retrying err=“state data download canceled (requested)”

Musicoin Wallet stderr: WARN [03-28|13:03:29] Skipping deep transaction reorg depth=2223836

Musicoin Wallet stderr: WARN [03-28|13:03:31] Ancestor below allowance peer=3add16e18bd55da6 number=2133836 hash=000000…000000 allowance=2133836

Musicoin Wallet stderr: WARN [03-28|13:03:31] Synchronisation failed, dropping peer peer=3add16e18bd55da6 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: INFO [03-28|13:03:37] Upgrading chain index type=bloombits percentage=6

Musicoin Wallet stderr: WARN [03-28|13:03:43] Ancestor below allowance peer=d330b1bd1a78dd0d number=2133836 hash=000000…000000 allowance=2133836
WARN [03-28|13:03:43] Synchronisation failed, dropping peer peer=d330b1bd1a78dd0d err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: INFO [03-28|13:03:45] Upgrading chain index type=bloombits percentage=13

Musicoin Wallet stderr: WARN [03-28|13:03:51] Ancestor below allowance peer=e4f43671b83d978d number=2133836 hash=000000…000000 allowance=2133836

Musicoin Wallet stderr: WARN [03-28|13:03:51] Synchronisation failed, dropping peer peer=e4f43671b83d978d err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: WARN [03-28|13:03:52] Ancestor below allowance peer=d3213f2911dd0e67 number=2133836 hash=000000…000000 allowance=2133836
WARN [03-28|13:03:52] Synchronisation failed, dropping peer peer=d3213f2911dd0e67 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: INFO [03-28|13:03:53] Upgrading chain index type=bloombits percentage=19

Musicoin Wallet stderr: WARN [03-28|13:03:53] Ancestor below allowance peer=627ff0d03e823952 number=2133836 hash=000000…000000 allowance=2133836

Musicoin Wallet stderr: WARN [03-28|13:03:53] Synchronisation failed, dropping peer peer=627ff0d03e823952 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: WARN [03-28|13:03:56] Ancestor below allowance peer=832cd42e33f304c2 number=2133836 hash=000000…000000 allowance=2133836
WARN [03-28|13:03:56] Synchronisation failed, dropping peer peer=832cd42e33f304c2 err=“retrieved ancestor is invalid”

Musicoin Wallet stderr: INFO [03-28|13:03:57] Imported new chain segment blocks=2 txs=90 mgas=0.870 elapsed=113.303ms mgasps=7.677 number=2223837 hash=653d6a…73dff4 ignored=9

Musicoin Wallet stderr: INFO [03-28|13:03:57] Imported new chain segment blocks=16 txs=104 mgas=4.785 elapsed=208.554ms mgasps=22.942 number=2223853 hash=e2fb88…8cbce4

Musicoin Wallet stderr: INFO [03-28|13:03:58] Imported new chain segment blocks=1 txs=8 mgas=0.237 elapsed=15.040ms mgasps=15.777 number=2223854 hash=950b13…8d9b45

Musicoin

administrators

@MJMoonbow-aka-Tinman I didn’t see anything shady all as expected. Still a lot nodes, non upgraded.

Looks like your connection to Musicoin Forum was lost, please wait while we try to reconnect.