Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Issues
  • #367

Closed
Open
Created Apr 06, 2020 by Mark Brooker@walkjiveflyMaintainer

Sync from bootstrap generates large platform/000003.log and performance is very poor

Summary

Syncing from bootstrap generates about 53MB of log file. If the wallet/node is shutdown and restarted a *.ldb file is written and the log is cleared.

Possibly related to this, the sync from bootstrap performance is MUCH worse than it used to be. On my machine, as recently as a couple of months ago, it used to take an hour to fully sync. In testing the newest bootstrap (5 April 2020) the sync took about 7 hours.

Steps to reproduce

(Wipe out contents of blocks, chainstate and platform folders) Sync from bootstrap

Expected behavior

Recently this took about an hour.

Problematic behavior

Testing yesterday, sync from bootstrap took 7 hours.

Crown-core environment info

MX-Linux 18.3

Crown-core application info

Crown version v0.14.0.1-Emerald (2020-04-02 15:31:34 +0000)

Relevant logs, dumps and/or screenshots

mark@x230:~/.crown/platform$ ls -l
total 52404
-rw------- 1 mark mark 53641824 Apr  6 18:30 000003.log
-rw------- 1 mark mark       16 Apr  5 20:38 CURRENT
-rw------- 1 mark mark        0 Apr  5 20:38 LOCK
-rw------- 1 mark mark       57 Apr  5 20:38 LOG
-rw------- 1 mark mark       50 Apr  5 20:38 MANIFEST-000002
mark@x230:~/.crown/platform$ cd ..
mark@x230:~/.crown$ zip -r issue367 platform
  adding: platform/ (stored 0%)
  adding: platform/LOG (stored 0%)
  adding: platform/000003.log (deflated 100%)
  adding: platform/LOCK (stored 0%)
  adding: platform/MANIFEST-000002 (stored 0%)
  adding: platform/CURRENT (deflated 6%)
mark@x230:~/.crown$ crown-cli restart
Crown server restarting
mark@x230:~/.crown$ Crown server starting

mark@x230:~/.crown$ 
mark@x230:~/.crown$ ll platform
total 32
-rw------- 1 mark     0 Apr  5 20:38 LOCK
-rw------- 1 mark    57 Apr  5 20:38 LOG.old
-rw------- 1 mark 10872 Apr  6 18:44 000005.ldb
-rw------- 1 mark    83 Apr  6 18:44 MANIFEST-000004
-rw------- 1 mark    16 Apr  6 18:44 CURRENT
-rw------- 1 mark   311 Apr  6 18:44 LOG
-rw------- 1 mark    19 Apr  6 18:44 000006.log
mark@x230:~/.crown$ grep "Crown version" debug.log
2020-04-06 16:44:18 Crown version v0.14.0.1-Emerald (2020-04-02 15:31:34 +0000)

Uploaded issue367.zip to https://nextcloud.crownplatform.com/index.php/s/Q6H8enXNmJsQYCD

Possible fixes

(Any comments on what you think might be responsible for the problem, if you have particular insight.)

/cc @artem

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking