Write cache burns too much CPU #1527

Closed
opened 2025-12-28 17:35:43 +00:00 by sami · 1 comment
Owner

Originally created by @roman-khimov on GitHub (Oct 20, 2025).

Expected Behavior

Write cache not much visible in the profile.

Current Behavior

Image

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):
Originally created by @roman-khimov on GitHub (Oct 20, 2025). ## Expected Behavior Write cache not much visible in the profile. ## Current Behavior <img width="830" height="374" alt="Image" src="https://github.com/user-attachments/assets/9b1074b0-d36a-419f-882f-7b1507e3583a" /> ## 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`):
sami 2025-12-28 17:35:43 +00:00
Author
Owner

@roman-khimov commented on GitHub (Oct 20, 2025):

Allocated objects:

Image
@roman-khimov commented on GitHub (Oct 20, 2025): Allocated objects: <img width="833" height="168" alt="Image" src="https://github.com/user-attachments/assets/504208e6-6954-40f4-815c-a9264b68ed17" />
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1527
No description provided.