Benchmark: sha1-js-pref - MeasureThat.net

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/sjcl/1.0.6/sjcl.min.js"></script>
<script 
src="https://cdnjs.cloudflare.com/ajax/libs/rusha/0.8.7/rusha.js"></script>
<script
 src="https://cdnjs.cloudflare.com/ajax/libs/crypto-js/3.1.9-1/crypto-js.min.js"></script>
<script
 src="https://cdnjs.cloudflare.com/ajax/libs/forge/0.9.1/forge.min.js"></script>

Script Preparation code:

var data = new Uint32Array(1024);
  window.crypto.getRandomValues(data);
  var dataBuffer = new Uint8Array(data);
  data = String.fromCharCode.apply(null, dataBuffer);
  
  
  // src: https://developer.mozilla.org/en-US/docs/Web/API/SubtleCrypto/digest
  function hex(buffer) {
    var hexCodes = [];
    var view = new DataView(buffer);
    for (var i = 0; i < view.byteLength; i += 4) {
      // Using getUint32 reduces the number of iterations needed (we process 4 bytes each time)
      var value = view.getUint32(i)
      // toString(16) will give the hex representation of the number without padding
      var stringValue = value.toString(16)
      // We use concatenation and slice for padding
      var padding = '00000000'
      var paddedValue = (padding + stringValue).slice(-padding.length)
      hexCodes.push(paddedValue);
    }
  
    // Join all the hex strings into one
    return hexCodes.join("");
  }

Tests:

forge
forge.md.sha1.create().update(data).digest()
native
crypto.subtle.digest("SHA-1", dataBuffer ).then(function (hash) {console.log(hex(hash));});
sjcl
sjcl.hash.sha1.hash(data);
cryptojs
CryptoJS.SHA1(data);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
forge
native
sjcl
cryptojs

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 3 months ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Browser/OS: Chrome 131 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
forge	92697.0 Ops/sec
native	386541.2 Ops/sec
sjcl	0.0 Ops/sec
cryptojs	30184.7 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated 6 months ago):

LLMs can make mistakes. Check important info.

The provided JSON represents a JavaScript benchmark test case on MeasureThat.net. Let's break it down and explain what's being tested.

**Benchmark Definition**

The benchmark is designed to measure the performance of different libraries for generating SHA-1 hashes in JavaScript. The test creates a random data buffer using the Web Cryptography API (subtlecrypto) or a library, and then generates an SHA-1 hash using the corresponding function from each library.

**Options Compared**

Four options are being compared:

1. **Native**: Using the `crypto.subtle.digest` function from the Web Cryptography API.
2. **Forge**: Using the Forge library, which provides a simple way to perform cryptographic operations.
3. **SJCL**: Using the SJCL (Simple JavaScript Crypto Library) library, which is a lightweight implementation of various cryptographic algorithms.
4. **CryptoJS**: Using the CryptoJS library, which is a popular encryption library for JavaScript.

**Pros and Cons of Each Approach**

1. **Native**:
	* Pros: Built-in Web Cryptography API, low overhead, easy to use.
	* Cons: Limited support on older browsers, may require additional setup for some features.
2. **Forge**: 
	* Pros: Simple and lightweight, good performance, supports a wide range of cryptographic algorithms.
	* Cons: May not be as performant as native or CryptoJS for very large data sets, limited support on older browsers.
3. **SJCL**:
	* Pros: Lightweight, easy to use, fast, supports SHA-1 hash generation.
	* Cons: Limited features compared to other libraries, may not be suitable for complex cryptographic operations.
4. **CryptoJS**: 
	* Pros: Feature-rich, widely supported, good performance.
	* Cons: Larger overhead compared to native or Forge, more complex API.

**Library Descriptions**

1. **Forge**: The Forge library is a lightweight implementation of various cryptographic algorithms, including SHA-1 hash generation. It's designed to be easy to use and provides fast performance.
2. **SJCL**: The SJCL (Simple JavaScript Crypto Library) library is a simple and lightweight implementation of cryptographic algorithms, including SHA-1 hash generation. It's designed for simplicity and ease of use.
3. **CryptoJS**: The CryptoJS library is a popular encryption library for JavaScript that provides a wide range of features, including support for SHA-1 hash generation.

**Special JS Features**

The test case uses the following special JavaScript feature:

* Web Cryptography API (subtlecrypto): This API provides a way to perform cryptographic operations in web applications. It's supported by most modern browsers and allows for more efficient and secure cryptographic operations compared to traditional libraries like CryptoJS or SJCL.

**Other Alternatives**

If you're looking for alternative libraries for generating SHA-1 hashes, some popular options include:

* **Crypto-JS**: A widely used encryption library for JavaScript that provides a simple way to perform cryptographic operations.
* **Secure-SHA**: A lightweight implementation of the Secure Hash Algorithm (SHA) family, including SHA-1 hash generation.
* **webcrypto-js**: A JavaScript implementation of the Web Cryptography API, which provides a more efficient and secure way to perform cryptographic operations.

In conclusion, the test case on MeasureThat.net compares the performance of different libraries for generating SHA-1 hashes in JavaScript. The options compared include native, Forge, SJCL, and CryptoJS. Each library has its pros and cons, and the choice of library depends on the specific requirements of your project, including performance, complexity, and feature support.

Related benchmarks:

sha1-js-pref (version: 0)

Comparing performance of: forge vs native vs sjcl vs cryptojs

Created: 5 years ago by: Guest

Jump to the latest result

forge

native

sjcl

cryptojs

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 6 months ago):