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

Closed
Open
Created May 04, 2018 by Josh Wilcox@finjoshDeveloper

Investigate possible memory leaks in QT wallet, causing bad lag

It really impacts UX of the wallet, especially when voting. Users have experienced lag, periods of no activity then a period of no instability then periods of instability again (intermittent freezing). According to @defunctec it seems the more UTXO in the wallet the slower it gets, and this could be due to for instance a hundred system nodes running out of the same wallet.

We need to look at the wallet code and design a solution allowing it to take advantage of n-core CPU cycles to increase performance. The user expects that the client software not lag in any circumstance for >500ms, the threshold of which this single-core limit has passed by an order of magnitude (up to 5000ms wait times experienced).

Edited May 11, 2018 by Josh Wilcox
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking