Add other checksum types #11
Labels
No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api#11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We can set it on client, sha256 is still supported.
SHA-512 seems somewhat faster on 64-bit processors:
We could benchmark, and, if it makes sense, support another checksum.
In this task let's do some research and benchmarks on a hardware.
BLAKE* is another candidate.
It would be nice to use container attribute to determine required hashing algorithm for each new object.