carpawell

>> So what is the peapod's fate? > > TBD I am asking cause we have to rework some things if there is no "small" storage anymore. ___ Have you...

> Have you considered GET bench? Isn't it slower to read a combined object for only a part of it if there are a few parallel GET requests? Like reading...

I think with some paraphrasing it duplicates https://github.com/nspcc-dev/neofs-node/issues/2692.

According to @roman-khimov's > In fact this suggests not repeating attempts as well. i found this issue was about caching.

> all components currently process storage policies independently Can we unify it?

@fyrchik, it affects more than one component. I expect to create some set of issues and link them with that epic. But after a discussion.

> one disk that stores metabase(s) > storage: > metabase: > path: /srv/neofs/ssd/meta Is it ok to lose every metabase at once?

@roman-khimov, did not know #2317 exists. Initially planned this issue to be a general issue with some discussion. Can be reworked/renamed.

> Searching for a city is a more natural thing. This issue is about the case when you do not have your city but need to specify some.

Not sure why there is no "tree" word here but it was about it only. Anyway does not seem actual.