mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Write cache burns too much CPU #1527
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1527
Loading…
Add table
Add a link
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?
Originally created by @roman-khimov on GitHub (Oct 20, 2025).
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
uname -a):@roman-khimov commented on GitHub (Oct 20, 2025):
Allocated objects: