[#2] hrw: add typed methods for hashers #3
Labels
No labels
P0
P1
P2
P3
good first issue
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/hrw#3
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/refactor-hrw"
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?
Add generic methods for sort-methods used in node
Could you also add
benchstat
output (or just benchmark result) in the commit message?@ -1,8 +1,13 @@
module github.com/TrueCloudLab/hrw
go 1.14
go 1.18
Worth a separate commit.
s/received/receives/
dot in the end of the comment: there is a linter which complains + Godoc is nicer.
@ -1,8 +1,13 @@
module github.com/TrueCloudLab/hrw
go 1.14
go 1.18
fixed
fixed
BB
?Frankly, I would rather delete this from README -- raw numbers, without any explanation or meaningful implications. Or, maybe at least add CPU model/RAM capacity. Like in this diff: the numbers have changed even though for most of the benchmarks the code is the same.
Not in this PR, of course. cc @alexvanin
What does the last commit mean? Also, agree with @fyrchik that comparing (before/after on the same machine) results somewhere (e.g. commit msg) would be nice.
git command typo, fixed.
There is no fixes in existed methods, so no diff in existed benchmarks.