You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
emhane opened this issue
Jun 28, 2024
· 2 comments
Labels
A-pruningRelated to pruning or full nodeC-perfA change motivated by improving speed, memory usage or disk footprintS-wontfixThis issue is the result of a deliberate design decision, and will not be fixed
It's best to take a write lock as late as possible. Therefore, pruner should pass a reference to ProviderFactory to segments, instead of take the write lock before calling Segment::prune.
This is the first step in making it possible to take only a read lock on db in history pruning.
Additional context
No response
The text was updated successfully, but these errors were encountered:
emhane
added
C-perf
A change motivated by improving speed, memory usage or disk footprint
A-pruning
Related to pruning or full node
labels
Jun 28, 2024
A-pruningRelated to pruning or full nodeC-perfA change motivated by improving speed, memory usage or disk footprintS-wontfixThis issue is the result of a deliberate design decision, and will not be fixed
Describe the feature
It's best to take a write lock as late as possible. Therefore, pruner should pass a reference to
ProviderFactory
to segments, instead of take the write lock before callingSegment::prune
.This is the first step in making it possible to take only a read lock on db in history pruning.
Additional context
No response
The text was updated successfully, but these errors were encountered: