Refactor working with container list #175

Closed
opened 2023-03-24 10:25:09 +00:00 by fyrchik · 2 comments
Owner

In #172 we removed a technical limitation regarding containers number, but replaced it with another one instead: container list must reside in RAM.

While the number of containers won't, most likely, be not THAT big, there are other problems:

  1. Listing latency. We don't want to wait for another hour just to fetch 32M containers.
  2. Our system is intended to be as scalable as possible, let's keep the promise.
In #172 we removed a technical limitation regarding containers number, but replaced it with another one instead: container list must reside in RAM. While the number of containers won't, most likely, be not THAT big, there are other problems: 1. Listing latency. We don't want to wait for another hour just to fetch 32M containers. 2. Our system is intended to be as scalable as possible, let's keep the promise.
fyrchik added the
triage
label 2023-03-24 10:25:09 +00:00
fyrchik added the
frostfs-node
label 2023-03-24 10:57:31 +00:00
acid-ant was assigned by fyrchik 2023-04-03 16:05:25 +00:00
acid-ant was unassigned by fyrchik 2023-04-03 16:05:41 +00:00
Author
Owner

I am not sure how to do it for the tree synchronization: synchronization time can be much more than iterator session lifetime.

I am not sure how to do it for the tree synchronization: synchronization time can be much more than iterator session lifetime.
fyrchik added this to the vNext milestone 2023-05-18 08:33:25 +00:00
fyrchik added the
P3
label 2024-01-16 12:30:04 +00:00
Author
Owner

If we use the iterator, it will take some of the neo-go resources.
There are lots of problems with sessions which seem more severe (we have already encountered some), closing this issue.

If we use the iterator, it will take some of the neo-go resources. There are lots of problems with sessions which seem more severe (we have already encountered some), closing this issue.
fyrchik modified the milestone from vNext to v0.39.0 2024-05-02 07:38:06 +00:00
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: TrueCloudLab/frostfs-node#175
No description provided.