https://github.com/macdja38/salt-bench-test

https://github.com/macdja38/salt-bench-test

benchmark buffer libsodium nodejs pool sodium

Last synced: 28 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/macdja38/salt-bench-test
• Owner: macdja38
• Created: 2017-02-06T03:11:13.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2017-02-06T09:30:11.000Z (almost 8 years ago)
• Last Synced: 2024-10-22T09:54:01.889Z (3 months ago)
• Topics: benchmark, buffer, libsodium, nodejs, pool, sodium
• Language: JavaScript
• Size: 2.93 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# salt-bench-test

Benchmark suit setup to test readily available libsodium builds secretbox encrypting speed

Run on an i7 3770k with 1330hz DDR3 memory it results in

  ```

  sodium x 26,360 ops/sec ±4.68% (83 runs sampled)

  sodium-native x 29,325 ops/sec ±1.23% (92 runs sampled)

  sodium-native-pool x 30,828 ops/sec ±0.74% (89 runs sampled)

  sodium-native-same-buffer x 30,032 ops/sec ±2.09% (88 runs sampled)

  sodiumEncryption x 14,017 ops/sec ±2.30% (82 runs sampled)

  tweetnacl x 16,522 ops/sec ±2.19% (82 runs sampled)

  Fastest is sodium-native-pool,sodium-native-same-buffer

  ```

If you would like another library added to this please create an issue or submit a pr, if you have any reason to believe this test may be giving one library an unfair advantage please inform me.

the sodium-native-pool and sodium-same-buffer are tests to attempt to take into account the different method of outputting values, instead of returning a result sodium-native writes it into an existing buffer which from my personal understanding can be used to improve preformance by reducing object creation. The sodium-native-pool test may well be flawed but was designed to simulate array operations to handle a pool that could possibly be recycled.