Benchmark: luxon-v-Intl-v-datefns format, luxon-v-Date-v-datefns native parse

HTML Preparation code:

<script src="https://cdn.jsdelivr.net/npm/luxon@2.0.2/build/global/luxon.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/date-fns/1.29.0/date_fns.min.js"></script>

Script Preparation code:

window.__dateISO__ = '2021-09-24T07:36:51+0000'
window.__date__ = new Date(__dateISO__);
window.__expected__ = '09/24/2021';
window.__intlFormatter = new Intl.DateTimeFormat('en', {
  year: '2-digit',
  month: '2-digit',
  day: '2-digit',
});

Tests:

moment/luxon - format
var actual = luxon.DateTime.fromJSDate(__date__).toLocaleString(); console.assert(actual === __expected__);
Intl - format
var actual = window.__intlFormatter.format(__date__); console.assert(actual === __expected__);
moment/luxon - parse
var actual = luxon.DateTime.fromISO(__dateISO__).toJSDate(); console.assert(__date__.getTime() === actual.getTime());
Native parse
var actual = new Date(__dateISO__); console.assert(__date__.getTime() === actual.getTime());
date-fns (old) format
var actual = dateFns.format(__date__); console.assert(actual === __expected__);
date-fns (old) parse
var actual = dateFns.parse(__dateISO__); console.assert(__date__.getTime() === actual.getTime());

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
moment/luxon - format
Intl - format
moment/luxon - parse
Native parse
date-fns (old) format
date-fns (old) parse

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

**Overview of the Benchmark**

The provided JSON represents a JavaScript microbenchmarking test case on MeasureThat.net. The benchmark tests the performance of various libraries for formatting and parsing date strings. The main objective is to compare the execution speed of different approaches for converting between different date formats.

**Options Compared**

The following options are compared in this benchmark:

1. **Native Parse (Luxon)**: This option uses the `luxon` library's native parsing functionality.
2. **Moment/Luxon Parse**: This option uses a combination of the `moment.js` and `luxon` libraries for parsing dates.
3. **Date-fns (Old) Parse**: This option uses the older version of the `date-fns` library for parsing dates.
4. **Intl Format**: This option uses the `Intl.DateTimeFormat` API to format dates.
5. **Moment/Luxon Format**: This option uses a combination of the `moment.js` and `luxon` libraries for formatting dates.

**Pros and Cons**

Here are some pros and cons of each approach:

1. **Native Parse (Luxon)**:
	* Pros: Fastest execution speed, no dependencies on other libraries.
	* Cons: May require more code to implement, not as widely supported as other options.
2. **Moment/Luxon Parse**:
	* Pros: More widely supported than native parse, can leverage moment.js's parsing capabilities.
	* Cons: Slower execution speed due to the overhead of multiple library dependencies.
3. **Date-fns (Old) Parse**:
	* Pros: Smaller dependency footprint compared to moment/luxon parse, still relatively fast.
	* Cons: Older version of date-fns may not be as efficient or feature-rich as newer versions.
4. **Intl Format**:
	* Pros: Standardized API across browsers, can format dates without relying on third-party libraries.
	* Cons: May require more code to implement, slower execution speed compared to native parse.
5. **Moment/Luxon Format**:
	* Pros: Combines the benefits of both moment.js and luxon libraries for formatting dates.
	* Cons: Slower execution speed due to the overhead of multiple library dependencies.

**Library Descriptions**

1. **Luxon**: A modern, open-source date and time library developed by Amund Arnetz.
2. **Moment.js**: A widely-used JavaScript library for working with dates and times, originally created by Scott Berkun.
3. **Date-fns**: A smaller, fast, and efficient date manipulation library developed by Julius Kashtanov.

**Special JS Feature/Syntax**

The benchmark uses the `__dateISO__` variable to represent a date string in ISO 8601 format, and the `__intlFormatter` object to perform formatting using the Intl.DateTimeFormat API. The `__date` variable represents the original date value used in the benchmark.

**Other Alternatives**

If you're interested in exploring alternative libraries or approaches for date manipulation in JavaScript, here are some options:

* **Day.js**: A lightweight, modern date and time library developed by Nick Zakas.
* **Moment.js 2.x**: The newer version of moment.js with improved performance and features.
* **Date-Picker**: A lightweight, fast, and efficient date picker library developed by Andrew Welch.

I hope this helps! Let me know if you have any further questions.

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

Browser/OS: Chrome 127 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
moment/luxon - format	288845.5 Ops/sec
Intl - format	362642.2 Ops/sec
moment/luxon - parse	643490.1 Ops/sec
Native parse	3270618.5 Ops/sec
date-fns (old) format	267378.3 Ops/sec
date-fns (old) parse	1225483.2 Ops/sec

Related benchmarks:

luxon-v-Intl-v-datefns format, luxon-v-Date-v-datefns native parse (version: 0)

Comparing performance of: moment/luxon - format vs Intl - format vs moment/luxon - parse vs Native parse vs date-fns (old) format vs date-fns (old) parse

Created: 3 years ago by: Guest

Jump to the latest result

moment/luxon - format

Intl - format

moment/luxon - parse

Native parse

date-fns (old) format

date-fns (old) parse

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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