-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Labels
I4No visible changesNo visible changesS4RoutineRoutineU2Seriously plannedSeriously plannedbugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second
Milestone
Description
Expected Behavior
Write cache not much visible in the profile.
Current Behavior
Possible Solution
Find out why it burns cycles this much and fix it.
Steps to Reproduce (for bugs)
Run a node, check profile.
Context
Mainnet. This node does process around 1-5 objects per second which is not a lot, most of the time the cache is empty.
This node doesn't have #3641 problem.
Regression
Yes and no, write cache was seriously reworked in 0.46.0, the scheme works fine in general, but CPU consumption is somewhat problematic.
Your Environment
- Version used: 0.49.1
- Server setup and configuration:
- Operating System and version (
uname -a):
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
I4No visible changesNo visible changesS4RoutineRoutineU2Seriously plannedSeriously plannedbugSomething isn't workingSomething isn't workingneofs-storageStorage node application issuesStorage node application issuesperformanceMore of something per secondMore of something per second