<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1449498" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ManfredKarrer">@ManfredKarrer</a> Accessing the blockchain file is expected to be slower.<br>
Again, I don't know whether slower means a few nanoseconds or a couple of minutes. NonMMappedSPVBlockStore (and SPVBlockStore) implement a software cache, so most retrieval operations should not imply access to the blockchain file.</p>
<p>The performance degradation should be experienced always, but we can expect it to be worse when the blockchain file is used a lot.</p>
<p>During blockchain sync, blockchain file is written a lot, so that could be an interesting point to look at for performance degradation. Blockchain sync happens in 3 cases:</p>
<ul>
<li>new users</li>
<li>users who have not opened their wallets for a while</li>
<li>after restore from seed (actually, after the user restarts her wallet as the UI suggest on restore from seed)</li>
</ul>

<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/pull/2403#issuecomment-463339827">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtoCYpgGRfvDCPPt1ZmT71Yu8tukjks5vNGrdgaJpZM4a0Tob">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtk17VmMSEKA75sXyK57gRoNCbiNfks5vNGrdgaJpZM4a0Tob.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq","title":"bisq-network/bisq","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"PERSON","message":"@oscarguindzberg in #2403: @ManfredKarrer Accessing the blockchain file is expected to be slower.\r\nAgain, I don't know whether slower means a few nanoseconds or a couple of minutes. NonMMappedSPVBlockStore (and SPVBlockStore) implement a software cache, so most retrieval operations should not imply access to the blockchain file.\r\n\r\nThe performance degradation should be experienced always, but we can expect it to be worse when the blockchain file is used a lot.\r\n\r\nDuring blockchain sync, blockchain file is written a lot, so that could be an interesting point to look at for performance degradation. Blockchain sync happens in 3 cases:\r\n- new users\r\n- users who have not opened their wallets for a while\r\n- after restore from seed (actually, after the user restarts her wallet as the UI suggest on restore from seed)\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/bisq-network/bisq/pull/2403#issuecomment-463339827"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/2403#issuecomment-463339827",
"url": "https://github.com/bisq-network/bisq/pull/2403#issuecomment-463339827",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>