Reduce allocations for message verifications #3

New Issue

Open

opened 2023-02-03 14:08:02 +00:00 by fyrchik · 0 comments

fyrchik commented

2023-02-03 14:08:02 +00:00

(Migrated from github.com)

We do it often (everything is signed in FrostFS) and verification routines can be seen in benchmarks.
We should try to keep allocations as small as possible here.

Maybe, also implement a test like this one 2f2c5e41e7/src/crypto/ed25519/ed25519_test.go (L323)

We do it often (everything is signed in FrostFS) and verification routines can be seen in benchmarks. We should try to keep allocations as small as possible here. Maybe, also implement a test like this one https://github.com/golang/go/blob/2f2c5e41e7728cae99abd14e8bd5ffcfebf9df8e/src/crypto/ed25519/ed25519_test.go#L323

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] api-go: Go version up

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] signature: Refactor sign and verify

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] signature: Add benchmarks

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] signature: Sign parts in parallel

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] signature: Verify parts in parallel

fyrchik referenced this issue from a commit

2023-03-10 10:54:48 +00:00

[#3] signature: Add buffer pool

Sign in to join this conversation.

No Label

good first issue

No Milestone

No Assignees

1 Participants

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-api-go#3

There is no content yet.