node: Optimize verification of the request signatures #1167

New issue

Open

opened 2025-12-28 17:22:01 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:22:01 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 18, 2023).

NeoFS API server sometimes wastes large amounts of memory. For example, to verify request signatures, the server decodes messages into intermediate structures, encodes its parts (field-ordered Protocol Buffers V3), verifies signatures and request continues processing.

Describe the solution you'd like

do not perform extra decode-encode stages. To do this, we must arrange the fields in the message without an additional buffer, calculate the checksum and verify the signature. Nothing blocks us from this cuz Protobuf is pretty simple and gRPC lib provides a lot of utilities around it

Describe alternatives you've considered

leave as it is: simpler code but worse performance

Originally created by @cthulhu-rider on GitHub (Dec 18, 2023). ## Is your feature request related to a problem? Please describe. NeoFS API server sometimes wastes large amounts of memory. For example, to verify request signatures, the server decodes messages into intermediate structures, encodes its parts (field-ordered Protocol Buffers V3), verifies signatures and request continues processing. ## Describe the solution you'd like do not perform extra decode-encode stages. To do this, we must arrange the fields in the message without an additional buffer, calculate the checksum and verify the signature. Nothing blocks us from this cuz Protobuf is pretty simple and gRPC lib provides a lot of utilities around it ## Describe alternatives you've considered leave as it is: simpler code but worse performance

sami added the

neofs-storage

performance

labels

2025-12-28 17:22:01 +00:00

sami commented

2025-12-28 17:22:01 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Jan 29, 2024):

lets postpone this issue a bit, several more fundamental optimizations are coming with v0.40. It'd better to intro current optimization above those ones

@cthulhu-rider commented on GitHub (Jan 29, 2024): lets postpone this issue a bit, several more fundamental optimizations are coming with [v0.40](https://github.com/nspcc-dev/neofs-node/milestone/56). It'd better to intro current optimization above those ones