Identity/AttachedServices/Key Stretching Performance Tests: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "''This page is work in progres....'' {| border="1" cellpadding="2" |+ Test Results |- ! Browser / Test !! Firefox 23 Desktop !! Google Chrome !! Firefox Android Beta 24 !! Fi...")
 
No edit summary
Line 2: Line 2:


{| border="1" cellpadding="2"
{| border="1" cellpadding="2"
|+ Test Results
|+ Test Results (in ops/sec)
|-
|-
! Browser / Test !! Firefox 23 Desktop !! Google Chrome !! Firefox Android Beta 24 !! Firefox OS !! Android WebView  
! Browser / Test !! Firefox 23 Desktop !! Google Chrome 28 !! Firefox Android Beta 24 !! Firefox OS !! Android WebView  
|-
|-
! [1] pbkdf2 key
! [1] pbkdf2 key
| 0 || 0 || 0 || 0 || 0
| 5.39 ops/sec ±4.20% (30 runs sampled) || 8.12 ops/sec ±1.15% (43 runs sampled) || 0 || 0.24 ops/sec ±7.06% (6 runs sampled)  || 0
|-
|-
! [2] Key Stretch w/ Remote Helper
! [2] Key Stretch w/ Remote Helper
| 0 || 0 || 0 || 0 || 0
| 0.66 ops/sec ±10.70% (8 runs sampled) || 0.79 ops/sec ±1.98% (8 runs sampled) || 0 || 0 || 0
|-
|-
|}
|}
Line 16: Line 16:


'''Tests'''
'''Tests'''
* [1] ...
* [1] gherkin.pdbkdf2.derive(...) - Client pdbkdf2 derivation
* [2] ...
* [2] gherkin.keyStretch.derive(email, password) - Full Key Stretch with a remote helper at "http://scrypt.dev.lcip.org/".  




Line 26: Line 26:
* "ops/sec" stands for operations per second. That is how many times a test is projected to execute in a second.
* "ops/sec" stands for operations per second. That is how many times a test is projected to execute in a second.
* A test is repeatedly executed until it reaches the minimum time needed to get a percentage uncertainty for the measurement of less than or equal to 1%. The number of iterations will vary depending on the resolution of the environment’s timer and how many times a test can execute in the minimum run time. We collect completed test runs for 5 seconds (configurable), or at least 5 runs (also configurable), and then perform statistical analysis on the sample. So, a test may be repeated 100,000 times in 50 ms (the minimum run time for most environments), and then repeated 100 times more (5 seconds). A larger sample size (in this example, 100), leads to a smaller margin of error.
* A test is repeatedly executed until it reaches the minimum time needed to get a percentage uncertainty for the measurement of less than or equal to 1%. The number of iterations will vary depending on the resolution of the environment’s timer and how many times a test can execute in the minimum run time. We collect completed test runs for 5 seconds (configurable), or at least 5 runs (also configurable), and then perform statistical analysis on the sample. So, a test may be repeated 100,000 times in 50 ms (the minimum run time for most environments), and then repeated 100 times more (5 seconds). A larger sample size (in this example, 100), leads to a smaller margin of error.
Test Suite Page: [http://v14d.com/picl/benchmark.html http://v14d.com/picl/benchmark.html]
Confirmed users
43

edits

Navigation menu