Benchmark: URL params - MeasureThat.net

Script Preparation code:

var getURLParameters = url =>
  (url.match(/([^?=&]+)(=([^&]*))/g) || []).reduce(
    (a, v) => (
      (a[v.slice(0, v.indexOf('='))] = v.slice(v.indexOf('=') + 1)), a
    ),
    {}
  );

function getQueryParams(queryString) {
  queryString = queryString.split('+').join(' ');

  const params = {};
  let tokens;
  const re = /[?&]?([^=]+)=([^&]*)/g;

  // eslint-disable-next-line no-cond-assign
  while ((tokens = re.exec(queryString))) {
    params[decodeURIComponent(tokens[1])] = decodeURIComponent(tokens[2]);
  }

  return params;
}

Tests:

getURLParameters
getURLParameters("http://url.com/page?name=Adam&surname=Smith")
getQueryParams
getQueryParams("http://url.com/page?name=Adam&surname=Smith")

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
getURLParameters
getQueryParams

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 2 years ago)

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

Browser/OS: Chrome 103 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
getURLParameters	962097.5 Ops/sec
getQueryParams	500900.9 Ops/sec

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

LLMs can make mistakes. Check important info.

I'll break down the provided benchmark and explain what's being tested, compared, and other considerations.

**Benchmark Definition JSON**

The benchmark definition represents two JavaScript functions: `getURLParameters` and `getQueryParams`. These functions are used to extract URL parameters from a given URL string.

**What is tested?**

Two test cases are provided:

1. `getURLParameters`: Tests the performance of the `getURLParameters` function, which takes a URL string as input and returns an object with extracted URL parameters.
2. `getQueryParams`: Tests the performance of the `getQueryParams` function, which also takes a URL string as input but uses a different implementation to extract URL parameters.

**Options compared**

The benchmark compares two approaches for extracting URL parameters:

1. **`getURLParameters`**: This function uses a regular expression (`/([^?=&]+)(=([^&]*))/g`) to match and extract URL parameter pairs. It then reduces the matched values into an object using JavaScript's `reduce()` method.
2. **`getQueryParams`**: This function splits the URL string by `+` characters, which separates query parameters, and then uses a regular expression (`[?&]?([^=]+)=([^&]*)/g`) to match and extract individual URL parameter pairs.

**Pros and Cons**

1. **`getURLParameters`**:
	* Pros: Simple and straightforward implementation using JavaScript's built-in `reduce()` method.
	* Cons: May not be as efficient as other approaches, especially for large URL strings or complex parameter names.
2. **`getQueryParams`**:
	* Pros: More flexible and efficient approach by splitting the URL string and using a single regular expression to match individual parameters.
	* Cons: Requires additional processing steps (splitting and decoding) which may impact performance.

**Library usage**

Neither of the provided functions uses any external libraries. They are pure JavaScript implementations.

**Special JS features or syntax**

None are mentioned in this benchmark. However, it's worth noting that some modern JavaScript features like `template literals` could be used to improve code readability and maintainability for more complex URL parameter extractions.

**Other alternatives**

Some alternative approaches for extracting URL parameters include:

1. Using a dedicated library like `url-params-parser` or `query-string`.
2. Implementing a custom parser using a different programming paradigm (e.g., using regex patterns in a language like Python).
3. Utilizing browser-specific APIs, such as Chrome's `URLSearchParams` API.

Keep in mind that each alternative approach may have its own pros and cons, and the chosen method should be tailored to specific use cases and performance requirements.

Related benchmarks:

URL params (version: 0)

Comparing performance of: getURLParameters vs getQueryParams

Created: 2 years ago by: Registered User

Jump to the latest result

getURLParameters

getQueryParams

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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