Sort EC rules by complexity and try simpler ones first #1497

New issue

Open

opened 2025-12-28 17:35:38 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:38 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Sep 8, 2025).

according to EC rules, various number of EC parts (objects) may be produced. Also, ParityPartNum tells max num of parts we can lose. Rules from one policy can differ greatly in the general case

for example, 3/1 and 12/4. For PUT, the first one is simpler in terms of object/RPC num. For GET, 1st one is always simpler/faster

Describe the solution you'd like

when handling EC rules, pre-sort them and handle simpler ones earlier

Additional context

#526
#3497

Originally created by @cthulhu-rider on GitHub (Sep 8, 2025). ## Is your feature request related to a problem? Please describe. according to EC [rules](https://github.com/nspcc-dev/neofs-node/blob/dd83657ebb1559ae59afca1bba1faa057550139c/internal/ec/ec.go#L19-L22), various number of EC parts (objects) may be produced. Also, `ParityPartNum` tells max num of parts we can lose. Rules from one policy can differ greatly in the general case for example, `3/1` and `12/4`. For PUT, the first one is simpler in terms of object/RPC num. For GET, 1st one is always simpler/faster ## Describe the solution you'd like when handling EC rules, pre-sort them and handle simpler ones earlier ## Additional context * #526 * #3497