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.

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

Benchmark readme file shows output of subset algorithms than actually tested #249

Open
RonEld opened this issue Jun 10, 2019 · 14 comments
Open

Comments

@RonEld
Copy link
Contributor

RonEld commented Jun 10, 2019

The benchmark applications shows only subset of the algorithms, while the actual application tests all of the algorithms:

  MD4                      :      12039 KB/s
  MD5                      :       6889 KB/s
  RIPEMD160                :       3787 KB/s
  SHA-1                    :       3744 KB/s
  SHA-256                  :       2066 KB/s
  SHA-512                  :        626 KB/s
  ARC4                     :       4323 KB/s
  3DES                     :        161 KB/s
  DES                      :        436 KB/s
  3DES-CMAC                :        153 KB/s
  AES-CBC-128              :        824 KB/s
  AES-CBC-192              :        701 KB/s
  AES-CBC-256              :        611 KB/s
  AES-CTR-128              :        825 KB/s
  AES-CTR-192              :        702 KB/s
  AES-CTR-256              :        610 KB/s
  AES-GCM-128              :        360 KB/s
  AES-GCM-192              :        335 KB/s
  AES-GCM-256              :        312 KB/s
  AES-CCM-128              :        363 KB/s
  AES-CCM-192              :        314 KB/s
  AES-CCM-256              :        277 KB/s
  AES-CMAC-128             :        724 KB/s
  AES-CMAC-192             :        627 KB/s
  AES-CMAC-256             :        552 KB/s
  AES-CMAC-PRF-128         :        723 KB/s
  CAMELLIA-CBC-128         :        610 KB/s
  CAMELLIA-CBC-192         :        469 KB/s
  CAMELLIA-CBC-256         :        469 KB/s
  BLOWFISH-CBC-128         :       1406 KB/s
  BLOWFISH-CBC-192         :       1406 KB/s
  BLOWFISH-CBC-256         :       1406 KB/s
  CTR_DRBG (NOPR)          :        593 KB/s
  CTR_DRBG (PR)            :        440 KB/s
  HMAC_DRBG SHA-1 (NOPR)   :        255 KB/s
  HMAC_DRBG SHA-1 (PR)     :        236 KB/s
  HMAC_DRBG SHA-256 (NOPR) :        207 KB/s
  HMAC_DRBG SHA-256 (PR)   :        207 KB/s
  RSA-2048                 :      25 ms/ public
  RSA-2048                 :     973 ms/private
  ECDSA-secp384r1          :     522 ms/sign
  ECDSA-secp256r1          :     355 ms/sign
  ECDSA-secp384r1          :    1004 ms/verify
  ECDSA-secp256r1          :     688 ms/verify
  ECDHE-secp384r1          :     958 ms/handshake
  ECDHE-secp256r1          :     664 ms/handshake
  ECDH-secp384r1           :     473 ms/handshake
  ECDH-secp256r1           :     329 ms/handshake
  ECDHE-Curve25519         :     564 ms/handshake
  ECDH-Curve25519          :     290 ms/handshake
DONE
@ciarmcom
Copy link
Member

@RonEld thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

11 similar comments
@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 4, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 9, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Dec 5, 2020

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@RonEld it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants