Benchmark: js-yaml vs yaml-js vs yaml

HTML Preparation code:

<script src="https://cdnjs.cloudflare.com/ajax/libs/yamljs/0.3.0/yaml.min.js"></script>
<script>window.YAML1 = YAML</script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/js-yaml/3.12.0/js-yaml.min.js"></script>
<script src="https://eemeli.org/yaml-playground/yaml.browser.js"></script>
<script>window.YAML2 = YAML</script>

Script Preparation code:

var yamlString = 'key1: val1\nkey2: 7';

Tests:

yaml-js
var dummy = YAML1.parse(yamlString);
js-yaml
var dummy = jsyaml.safeLoad(yamlString);
yaml
var dummy = YAML2.parse(yamlString)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
yaml-js
js-yaml
yaml

Fastest: N/A

Slowest: N/A

Latest run results:

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

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

Browser/OS: Chrome 148 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
yaml-js	668610.4 Ops/sec
js-yaml	1255035.6 Ops/sec
yaml	666218.2 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?**

The provided JSON represents a benchmarking test for three different YAML parsing libraries: js-yaml, yaml-js, and a third-party library called YAML (from the yamljs repository). The test measures the execution time it takes to parse a simple YAML string using each library.

**Options compared:**

We have two main options being compared:

1. **js-yaml**: A popular JavaScript YAML parser that supports both safe and unsafe modes.
2. **yaml-js**: Another popular JavaScript YAML parser that provides a safer alternative to js-yaml, with improved security features.
3. **YAML (from yamljs)**: The third-party library used by yaml-js, which provides the actual YAML parsing functionality.

**Pros and Cons of each approach:**

* **js-yaml**:
	+ Pros: Lightweight, fast execution times, and suitable for most use cases.
	+ Cons: May have security vulnerabilities if not used properly (unsafe mode).
* **yaml-js**:
	+ Pros: Safer alternative to js-yaml with improved security features, better error handling, and support for more YAML features.
	+ Cons: Slightly heavier than js-yaml due to additional safety checks.
* **YAML (from yamljs)**:
	+ Pros: Provides the most comprehensive YAML parsing functionality, with advanced features like schema validation.
	+ Cons: May have a higher execution time compared to js-yaml and yaml-js.

**Library description and purpose:**

* **js-yaml**: A JavaScript library for parsing and generating YAML data. It provides both safe and unsafe modes for parsing.
* **yaml-js**: A safer alternative to js-yaml, designed with security in mind. It uses the third-party YAML library (from yamljs) under the hood.

**Special JS feature or syntax:**

There are no special JavaScript features or syntax being used in this benchmarking test.

**Other alternatives:**

If you're looking for other YAML parsing libraries, here are a few examples:

* **yaml**: A lightweight YAML parser written in C++.
* **js-yaml-unsafe**: An older version of js-yaml that provides an unsafe mode for faster execution times (no longer maintained).
* **yaml-parser**: A simple and lightweight YAML parser written in JavaScript.

In summary, the benchmarking test compares three different YAML parsing libraries: js-yaml, yaml-js, and a third-party library called YAML from yamljs. The test measures the execution time it takes to parse a simple YAML string using each library, providing insights into their performance characteristics.

Related benchmarks:

js-yaml vs yaml-js vs yaml (version: 0)

Comparing performance of: yaml-js vs js-yaml vs yaml

Created: 3 years ago by: Guest

Jump to the latest result

yaml-js

js-yaml

yaml

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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