Skip to content

Build node lists for container/object once per request #4077

Description

@cthulhu-rider

Is your feature request related to a problem? Please describe.

container node sets are requested multiple times, at least for:

the same is true about container info:

this is excessive. Better to consider the state consistent for the entire request lifetime

cache can amortize the waste of resources

Describe the solution you'd like

get any consistent data only when needed and only once

Additional context

#1803

Activity

  1. added
    U4Nothing urgent
    S3Minimally significant
    I4No visible changes
    on Jul 9, 2026
  2. added this to the v0.57.0 milestone on Aug 20, 2026
  3. roman-khimov commented on Aug 20, 2026

    @roman-khimov
    Member

    This is especially relevant in cases we need to modify (hence, copy) these lists (like OID mapping).

  4. modified the milestones: v0.57.0, v0.58.0 on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I4No visible changesS3Minimally significantU4Nothing urgentenhancementImproving existing functionalityneofs-storageStorage node application issuesperformanceMore of something per second

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions