Benchmark: Compare string equals performance with case long strings: with IntlCollator

Script Preparation code:

var a = 'Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32. The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham.';
var b = 'Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32. The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham.';
var c = 'Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots in a piece of classical Latin literature from 45 BC, making it over 2000 years old. Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of "de Finibus Bonorum et Malorum" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in section 1.10.32. The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H.';
var config = {
    sensitivity: 'base'
};

var enCollator = new Intl.Collator('en', {
    usage: "search",
    sensitivity: "base"
});

Tests:

=== true
a.toLowerCase() === b.toLowerCase();
locale compare true
a.localeCompare(b, 'en', config);
=== false
a.toLowerCase() === c.toLowerCase();
locale compare false
a.localeCompare(c, 'en', config);
Intl.Collator true
enCollator.compare(a, b) === 0;
Intl.Collator false
enCollator.compare(a, c) === 0;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
=== true
locale compare true
=== false
locale compare false
Intl.Collator true
Intl.Collator false

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/119.0.0.0 Safari/537.36

Browser/OS: Chrome 119 on Mac OS X 10.15.7

View result in a separate tab

Intl.Collator true

10.7M/s

=== false

4.2M/s

=== true

4.0M/s

Intl.Collator false

1.4M/s

locale compare true

328K/s

locale compare false

280K/s

View exact numbers

Test name	Executions per second
✓ Intl.Collator true	10,745,337 Ops/sec
=== false	4,170,772 Ops/sec
=== true	3,983,773 Ops/sec
Intl.Collator false	1,409,003 Ops/sec
locale compare true	328,494 Ops/sec
locale compare false	280,066 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's dive into the world of JavaScript microbenchmarks.

**What is tested?**

MeasureThat.net tests three different approaches to comparing strings with varying cases:

1. `toLowerCase()` method: Compares two strings in lowercase.
2. `localeCompare()` method: Compares two strings using the locale-specific collation rules, which takes into account case sensitivity and other cultural nuances.
3. Comparison using an instance of `Intl.Collator`: Uses a Unicode-aware collator to compare two strings.

**Test cases**

The test cases are designed to exercise each approach individually:

* `=== true` and `=== false` tests compare two identical strings with different casing.
* `locale compare true` and `locale compare false` tests compare two strings with the same casing.
* `Intl.Collator true` and `Intl.Collator false` tests use an instance of `Intl.Collator` to compare two strings.

**Benchmarks**

The latest benchmark results show the performance differences between these approaches:

| Test Name | Browser | Device Platform | Operating System | Executions/Sec |
| --- | --- | --- | --- | --- |
| Intl.Collator true | Chrome 119 | Desktop | Mac OS X 10.15.7 | 10745337.0 |
| Intl.Collator false | Chrome 119 | Desktop | Mac OS X 10.15.7 | 4170771.75 |
| === true | Chrome 119 | Desktop | Mac OS X 10.15.7 | 3983773.0 |
| === false | Chrome 119 | Desktop | Mac OS X 10.15.7 | 1409003.125 |
| locale compare true | Chrome 119 | Desktop | Mac OS X 10.15.7 | 328493.5 |
| locale compare false | Chrome 119 | Desktop | Mac OS X 10.15.7 | 280065.65625 |

**Key observations**

* `Intl.Collator` is the fastest approach, followed closely by `localeCompare()`.
* The order of comparison using `toLowerCase()` is slower compared to the other two approaches.
* There's a significant difference in performance between identical strings with different casing (`=== true`) and strings with the same casing but differing content (`locale compare true`).

These results demonstrate the importance of choosing the right approach for string comparisons, considering both performance and cultural nuances.

Compare string equals performance with case long strings: with IntlCollator (version: 0) Benchmark.js

Comparing performance of: `=== true vs locale compare true vs === false vs locale compare false vs Intl.Collator true vs Intl.Collator false`

Created: 2 years ago by: Guest

Go to the latest result

=== true

locale compare true

=== false

locale compare false

Intl.Collator true

Intl.Collator false

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Compare string equals performance with case long strings: with IntlCollator (version: 0) Benchmark.js

Comparing performance of: === true vs locale compare true vs === false vs locale compare false vs Intl.Collator true vs Intl.Collator false

Created: 2 years ago by: Guest

Go to the latest result

=== true

locale compare true

=== false

locale compare false

Intl.Collator true

Intl.Collator false

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: `=== true vs locale compare true vs === false vs locale compare false vs Intl.Collator true vs Intl.Collator false`