@@ -430,28 +430,28 @@ Benchmarks
430
430
----------
431
431
432
432
For reference, here are benchmarks from MacBook Pro (Retina, 13-inch, Mid 2014)
433
- laptop with 2.6 GHz Intel Core i5 CPU (Intel) in Chrome 53 /OS X and Xiaomi Redmi
433
+ laptop with 2.6 GHz Intel Core i5 CPU (Intel) in Chrome 62 /OS X and Xiaomi Redmi
434
434
Note 3 smartphone with 1.8 GHz Qualcomm Snapdragon 650 64-bit CPU (ARM) in
435
- Chrome 52 /Android:
435
+ Chrome 62 /Android:
436
436
437
437
| | nacl.js Intel | nacl-fast.js Intel | nacl.js ARM | nacl-fast.js ARM |
438
438
| ------------- | :-------------:| :-------------------:| :-------------:| :-----------------:|
439
- | salsa20 | 1.3 MB/s | 128 MB/s | 0 .4 MB/s | 43 MB/s |
440
- | poly1305 | 13 MB/s | 171 MB/s | 4 MB/s | 52 MB/s |
439
+ | salsa20 | 13 MB/s | 128 MB/s | 4 .4 MB/s | 43 MB/s |
440
+ | poly1305 | 10 MB/s | 195 MB/s | 2 MB/s | 76 MB/s |
441
441
| hash | 4 MB/s | 34 MB/s | 0.9 MB/s | 12 MB/s |
442
- | secretbox 1K | 1113 op/s | 57583 op/s | 334 op/s | 14227 op/s |
443
- | box 1K | 145 op/s | 718 op/s | 37 op/s | 368 op/s |
444
- | scalarMult | 171 op/s | 733 op/s | 56 op/s | 380 op/s |
445
- | sign | 77 op/s | 200 op/s | 20 op/s | 61 op/s |
446
- | sign.open | 39 op/s | 102 op/s | 11 op/s | 31 op/s |
442
+ | secretbox 1K | 5704 op/s | 79980 op/s | 334 op/s | 32949 op/s |
443
+ | box 1K | 148 op/s | 1039 op/s | 37 op/s | 576 op/s |
444
+ | scalarMult | 171 op/s | 1011 op/s | 56 op/s | 450 op/s |
445
+ | sign | 77 op/s | 498 op/s | 22 op/s | 218 op/s |
446
+ | sign.open | 39 op/s | 257 op/s | 12 op/s | 130 op/s |
447
447
448
448
(You can run benchmarks on your devices by clicking on the links at the bottom
449
449
of the [ home page] ( https://tweetnacl.js.org ) ).
450
450
451
451
In short, with * nacl-fast.js* and 1024-byte messages you can expect to encrypt and
452
- authenticate more than 57000 messages per second on a typical laptop or more than
453
- 14000 messages per second on a $170 smartphone, sign about 200 and verify 100
454
- messages per second on a laptop or 60 and 30 messages per second on a smartphone,
452
+ authenticate more than 75000 messages per second on a typical laptop or more than
453
+ 32000 messages per second on a $170 smartphone, sign about 500 and verify 250
454
+ messages per second on a laptop or 220 and 130 messages per second on a smartphone,
455
455
per CPU core (with Web Workers you can do these operations in parallel),
456
456
which is good enough for most applications.
457
457
0 commit comments