Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement benchmarks #4

Closed
14 of 15 tasks
clintfred opened this issue Oct 2, 2018 · 0 comments
Closed
14 of 15 tasks

Implement benchmarks #4

clintfred opened this issue Oct 2, 2018 · 0 comments
Assignees
@clintfred

Comments

@clintfred
Copy link
Contributor

clintfred commented Oct 2, 2018 •
edited
Loading

As a developer
I want to be able to measure the effect various changes have on the performance of recrypt's public API

AC:

  • - generate_key_pair
  • - generate_ed25519_key_pair
  • - generate_plaintext
  • - generate_transform_key
  • - compute_public_key
  • - derive_symmetric_key
  • - encrypt
  • - transform_to_level_1
  • - transform_to_level_2
  • - transform_to_level_3
  • - decrypt_from_level_0
  • - decrypt_from_level_1
  • - decrypt_from_level_2
  • - decrypt_from_level_3

optional:

  • - surface performance numbers in the README
@clintfred clintfred self-assigned this Oct 2, 2018
clintfred added a commit that referenced this issue Oct 4, 2018
@clintfred
[#4] WIP
e4f16c4
@clintfred clintfred mentioned this issue Oct 4, 2018
Merged
17 tasks
coltfred pushed a commit that referenced this issue Oct 5, 2018
@clintfred @coltfred
[#4] Add Api Benchmarks (#5)
df159dc 
* [#4] WIP

* * initial implementation of Api benchmarks

* * cleanup benchmarks file

* * cargo fmt

* Update to name the Ed25519Signature

* formatting

* * include `cargo bench` in README.md
@clintfred clintfred mentioned this issue Oct 17, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@clintfred clintfred

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ernieturner @clintfred