Skip to content

Conversation

@kohlschuetter
Copy link
Contributor

We currently only benchmark "encode" and "reconstruct" operations. (-corrupt 0 will actually corrupt up to M shards).

Introduce another special setting "-corrupt -1", which changes the benchmark to call enc.Verify instead of enc.Reconstruct.

Copy link
Owner

@klauspost klauspost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

We currently only benchmark "encode" and "reconstruct" operations.
(-corrupt 0 will actually corrupt up to M shards).

Introduce another special setting "-corrupt -1", which changes the
benchmark to call enc.Verify instead of enc.Reconstruct.
@kohlschuetter
Copy link
Contributor Author

My apologies for the force-push's, I just learned about gofmt

@klauspost
Copy link
Owner

My apologies for the force-push's, I just learned about gofmt

No worries :)

@klauspost klauspost merged commit bc3dc6f into klauspost:master Aug 8, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants