Benchmark: Dexie init - MeasureThat.net

HTML Preparation code:

<script src="https://unpkg.com/dexie@latest/dist/dexie.js"></script>
<script>
const getDb = () => {
  const skDatabase = new Dexie('skDatabase')
  skDatabase.version(1).stores({ communications: '++id' })
  return skDatabase
};
const getDbWithCaching = (() => {
  const db = getDb()
  return () => {
    return db
  }
})();
</script>

Tests:

no cache
getDb();
with caching
getDbWithCaching();

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 runs

with caching

121.1M/s

no cache

44K/s

Fastest: with caching (2760.6x faster)

View exact numbers

✓ with caching: 121,108,080 ops/sec
• no cache: 43,870 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
no cache
with caching

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 11 months ago)

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

Browser/OS: Chrome 141 on Windows

View result in a separate tab

with caching

147.6M/s

no cache

44K/s

View exact numbers

Test name	Executions per second
✓ with caching	147,632,288 Ops/sec
no cache	43,870 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's break down the benchmark definition and test cases.

**Benchmark Definition:**

The provided JSON represents a JavaScript microbenchmark that tests the initialization of the Dexie library, a popular offline database for web applications.

**Script Preparation Code:**

The script preparation code is a minimal setup to include the Dexie library in the HTML file:
```html
<script src="https://unpkg.com/dexie@latest/dist/dexie.js"></script>
```
This script includes the latest version of the Dexie library, which provides an asynchronous API for interacting with databases.

The actual initialization code is defined in a separate JavaScript block:
```javascript
const getDb = () => {
  const skDatabase = new Dexie('skDatabase');
  skDatabase.version(1).stores({ communications: '++id' });
  return skDatabase;
};

const getDbWithCaching = (() => {
  const db = getDb();
  return () => {
    return db;
  };
})();

// Note the immediately invoked function expression (IIFE) for caching
```
The `getDb()` function creates a new instance of the Dexie database, while `getDbWithCaching` returns the same instance wrapped in an IIFE. The latter is used to cache the result of `getDb()`, allowing subsequent calls to reuse the cached instance.

**Test Cases:**

There are two test cases:

1. **"no cache"**: This test case measures the execution time of calling `getDb()` directly without caching.
2. **"with caching"**: This test case measures the execution time of calling `getDbWithCaching()`, which uses caching to reuse the result of `getDb()`.

**Options Compared:**

The two test cases compare the performance difference between using caching (via IIFE) and not using caching (by directly calling `getDb()`).

**Pros and Cons:**

* **Caching (via IIFE):**
	+ Pros:
		- Reuses the result of `getDb()`, reducing overhead.
		- Can improve performance for repeated calls to `getDb()`.
	+ Cons:
		- Adds a layer of complexity with the IIFE, which may introduce unnecessary overhead.
		- May not be beneficial if `getDb()` is called only once or rarely.
* **No caching (direct call):**
	+ Pros:
		- Simpler and more straightforward implementation.
		- No added overhead from the IIFE.
	+ Cons:
		- Requires multiple calls to `getDb()` for repeated use, increasing overhead.

**Library:**

The Dexie library is a lightweight JavaScript framework for offline databases. Its purpose is to provide an asynchronous API for interacting with local storage or other data sources, allowing web applications to store and retrieve data even when the user is offline.

**Special JS Features/Syntax:**

* Immediately Invoked Function Expression (IIFE): Used in `getDbWithCaching` to create a cached version of `getDb()`. This syntax is used to execute the function immediately after its definition.
* Arrow Functions (`=>`): Used in `getDb()` and `getDbWithCaching` for concise function definitions.

**Alternatives:**

For offline databases, other popular alternatives include:

1. IndexedDB
2. PouchDB
3. LocalStorage

These libraries offer similar functionality to Dexie but with different approaches and features.

Dexie init (version: 0) Benchmark.js

Comparing performance of: `no cache vs with caching`

Created: 6 years ago by: Guest

Go to the latest result

no cache

with caching

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Dexie init (version: 0) Benchmark.js

Comparing performance of: no cache vs with caching

Created: 6 years ago by: Guest

Go to the latest result

no cache

with caching

Historical Performance Data aggregated from 5 community runs

Desktop Results:

Chrome 5 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: `no cache vs with caching`