need to increase the default dbcache size #237
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#237
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
getnameproof
fails to return the proof if there is not enough coin cache to roll back to the requested block. In the current release (12.2.3) it completely boggles the application state. In the current master it simply returns too early. We presently allow up to a 50 block rollback. Upstream bitcoin ups the dbcache to 450MB. Some rough calculations on our part show that we would need 1100MB to handle 50 full blocks. 50 full blocks is highly unlikely, but 450MB was insufficient for the use case recently demonstrated. That one required 700MB: Modify the max rollback to 5000 and rungetnameproof cuphead f231bbae207d4dc5ee6cf32b5f3ae87958acdc3a40a37e32cb46c95134419f39
. I propose that we up it to 700. That's not a steady state RAM usage, just an occasional spike.It depends of block size, maximum is 2MB but most of the time is pretty lower. We can set rollback to arbitrary value say ~1000 then we can throw out of memory exception, it'll be pretty noticeable what's going on.
#238
closed via #238