<p></p>
Do you get the same problem if you use a random seed with no txs associated<br>
to it and the same creation date?<br>
<br>
On Thu, Nov 19, 2020, 9:47 PM James Cox <notifications@github.com> wrote:<br>
<br>
><br>
>    - The wallet contains about 200 transactions.<br>
>    - Comparing 1.3.9 vs 1.4.2 right now, they have not finished but I'm<br>
>    certain from watching the progress that it will be the same result as above<br>
>    with 1.3.7 vs 1.4.2. (Already 1.3.9 is 2x the progress of 1.4.2 after 30<br>
>    minutes).<br>
>    - Yes, using all the defaults, out of the box fresh data directory<br>
>    installs of bisq.<br>
>    - The problem is synchronizing the bitcoin blockchain.<br>
><br>
> Some observations from watching the logs side-by-side:<br>
><br>
>    - 1.3.9 does its 3 allotment of stall disconnects in the first couple<br>
>    of minutes.<br>
>    - 1.4.2 starts off fast but soon the number of blocks received per<br>
>    second drops to a crawl -- however it does not stall/disconnect quickly<br>
>    like 1.3.9 does.<br>
>    - 1.3.9 seems to maintain a steady throughput of 20 blocks per sec<br>
>    quite consistently.<br>
>    - 1.4.2 slows to a crawl reporting 0 blocks per sec consistently,<br>
>    occasionally 1 block per sec.<br>
>    - 1.3.9 stall threshold = 1.56 KB/sec<br>
>    - 1.4.2 stall threshold = 0.78 KB/sec<br>
>    - Not a memory or CPU issue, its something like a timing issue to do<br>
>    with the way the requests are being made seems to cause the bitcoin nodes<br>
>    to be non-cooperative. That's my hunch. Throttling as @cbeams<br>
>    <https://github.com/cbeams> mentions here<br>
>    <https://github.com/bisq-network/bisq/issues/4778>.<br>
><br>
> —<br>
> You are receiving this because you were mentioned.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/bisq-network/bisq/issues/4807#issuecomment-730728963>,<br>
> or unsubscribe<br>
> <https://github.com/notifications/unsubscribe-auth/AAIXSLDPTUZ7UANVNNWXGPLSQW4AZANCNFSM4TVUCIGQ><br>
> .<br>
><br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/4807#issuecomment-730745564">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNQURHQ7GAHNXWWF7ULSQW6CXANCNFSM4TVUCIGQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNXQWSYJBF4JQZCI6HDSQW6CXA5CNFSM4TVUCIG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFOHEVXA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/4807#issuecomment-730745564",
"url": "https://github.com/bisq-network/bisq/issues/4807#issuecomment-730745564",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>