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
  • #336

Closed
Open
Created Dec 18, 2019 by Mark Brooker@walkjiveflyMaintainer

Excessive network usage when syncing from scratch

Summary

Excessive network use when synchronising the chain (~6GB) from scratch.

Steps to reproduce

Sync a new wallet/node from scratch. Observe the network usage

Expected behavior

Syncing a ~6GB chain really shouldn't need ~50GB download and ~30GB upload

Problematic behavior

A recent full sync from scratch used approximately

   RX bytes:51927074744 (51.9 GB)  TX bytes:27181023114 (27.1 GB)

as reported by ifconfig. Nothing else was running on the machine. This did include an apt-get update/upgrade (30MB max) and the initial code download (42MB max) and a few hours normal running after the sync completed. Everything else was syncing the chain.

Crown-core environment info

XUbuntu 16.04 LTS

Crown-core application info

Crown version v0.13.4.1-fd0432f6 pipeline build 6855

Relevant logs, dumps and/or screenshots

20191218_walkjivefly_wallet_excessive_network_usage_on_sync.zip uploaded to https://nextcloud.crownplatform.com/index.php/s/Q6H8enXNmJsQYCD

Possible fixes

We are presumably getting each block from multiple peers. I thought @presstab had changed the code to only pull blocks from at most 3 peers but that doesn't appear to be the case here.

A good workaround is to use the bootstrap for initial sync. The network usage for a full sync in that case was

   RX bytes:2513427536 (2.5 GB)  TX bytes:77641477 (77.6 MB)

/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