Benchmark: TextEncoder.encode() vs encodeURIComponent

Script Preparation code:

var str = "Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet."

Tests:

TextEncoder
new TextEncoder().encode(str)
encodeURIComponent
encodeURIComponent(str)

Historical Performance Data aggregated from 7 community runs

Desktop Results:

Chrome 7 runs

encodeURIComponent

663K/s

TextEncoder

512K/s

Fastest: encodeURIComponent (1.3x faster)

View exact numbers

✓ encodeURIComponent: 662,627 ops/sec
• TextEncoder: 511,704 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
TextEncoder
encodeURIComponent

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0

Browser/OS: Chrome 134 on Windows

View result in a separate tab

encodeURIComponent

627K/s

TextEncoder

512K/s

View exact numbers

Test name	Executions per second
✓ encodeURIComponent	626,781 Ops/sec
TextEncoder	511,704 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

**Benchmark Explanation**

The provided JSON represents a JavaScript benchmark that compares the performance of two encoding functions: `TextEncoder.encode()` and `encodeURIComponent()`. The test is designed to measure the execution speed of these functions on a given input string.

**Options Compared**

Two options are being compared:

1.  **`TextEncoder.encode()`**: This function is part of the Web APIs for working with binary strings, introduced in ECMAScript 2017 (ES7). It creates a text encoder that encodes a string to a new binary array.
2.  **`encodeURIComponent()`**: This function is part of the JavaScript Standard Library and takes a string as input and returns its encoded version using the URL encoding scheme.

**Pros and Cons**

*   **`TextEncoder.encode()`**
    *   Pros:
        *   More efficient and optimized for performance compared to `encodeURIComponent()`.
        *   Uses binary encoding, which can be more compact than URL-encoded strings.
    *   Cons:
        *   Not widely supported in older browsers or environments.
        *   Requires special handling for null or undefined inputs.

*   **`encodeURIComponent()`**
    *   Pros:
        *   Widely supported in older browsers and environments.
        *   Simpler to implement, as it uses a standard URL encoding scheme.
    *   Cons:
        *   Less efficient than `TextEncoder.encode()`, especially for large input strings.

**Library Usage**

None of the provided test cases explicitly use any external libraries. However, keep in mind that other libraries might be used elsewhere in your codebase to perform similar operations.

**Special JS Feature or Syntax**

The benchmark uses JavaScript's built-in `URLSearchParams` API (not mentioned in the given code snippet) which provides a simpler way to encode URLs, but it is not related to the `TextEncoder.encode()` and `encodeURIComponent()` functions being compared here. If you want to test more complex scenarios like encoding URLs or form data using this library, that would be another story.

**Other Alternatives**

If you need to compare other encoding options, consider exploring:

*   **`btoa()` (Binary to Text Encoding)**: This function encodes a binary string into a URL-encoded string.
*   **`new Blob()`**: Creates a new blob object from an array of bytes, which can be used as an alternative to `TextEncoder`.
*   **`JSON.stringify()` or `String.fromCharCode()`:** For encoding and decoding strings using a JSON-like syntax.

Keep in mind that these alternatives may have different performance characteristics compared to the functions being benchmarked.

TextEncoder.encode() vs encodeURIComponent (version: 0)

Comparing performance of: `TextEncoder vs encodeURIComponent`

Created: 4 years ago by: Guest

Go to the latest result

TextEncoder

encodeURIComponent

Historical Performance Data aggregated from 7 community runs

Desktop Results:

Chrome 7 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

TextEncoder.encode() vs encodeURIComponent (version: 0)

Comparing performance of: TextEncoder vs encodeURIComponent

Created: 4 years ago by: Guest

Go to the latest result

TextEncoder

encodeURIComponent

Historical Performance Data aggregated from 7 community runs

Desktop Results:

Chrome 7 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `TextEncoder vs encodeURIComponent`