Benchmark: EventStore projection

Tests:

isCategory First
const event = { streamId: "$et-SomeEvent", type: "$>" } const isCategory = event.streamId.includes("-") const isSystemCategoryOrSystemEvent = event.streamId.startsWith("$") || event.eventType.startsWith("$") var result = (!isCategory || isSystemCategoryOrSystemEvent)
systemEventFirst
const event = { streamId: "$et-SomeEvent", type: "$>" } const isCategory = event.streamId.includes("-") const isSystemCategoryOrSystemEvent = event.streamId.startsWith("$") || event.eventType.startsWith("$") var result = (isSystemCategoryOrSystemEvent || !isCategory)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
isCategory First
systemEventFirst

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

Let's break down the provided benchmark.

**What is being tested?**

The test is measuring the performance of two different approaches for determining whether an event is a system category or a system event. The approach involves checking if the `streamId` includes a hyphen (`-`) and/or starts with a specific prefix (`$`). The purpose of this test is likely to measure the speed of executing these conditional checks.

**Options compared:**

The two approaches being tested are:

1. **isCategory First**: This approach first checks if the event's `streamId` includes a hyphen, and then checks if it starts with the system category or system event prefix.
2. **systemEventFirst**: This approach first checks if the event is a system category or system event by checking if the `streamId` starts with the system category or system event prefix.

**Pros and Cons:**

* **isCategory First**:
	+ Pros: May be more intuitive for developers who are familiar with the system category concept.
	+ Cons: If the hyphen is not present, it may lead to false positives (i.e., incorrectly identifying a non-system category as a system event).
* **systemEventFirst**:
	+ Pros: Avoids potential false positives by directly checking for the presence of the prefix.
	+ Cons: May be less intuitive and more prone to errors if developers are not familiar with the system category concept.

**Library usage**

There is no explicit mention of a library being used in this benchmark. However, it's worth noting that the use of template literals (`const event = {...}`) and string interpolation (`$et-SomeEvent` and `$>` ) suggests that the benchmark may be targeting modern JavaScript engines that support these features.

**Special JS feature or syntax**

There is no explicit mention of a special JavaScript feature or syntax being used in this benchmark. However, it's worth noting that the use of double quotes (`"`) for string literals and template literals (`$` ) suggests that the benchmark may be targeting modern JavaScript engines that support these features.

**Other alternatives**

While there are only two options being compared in this benchmark, other approaches could include:

1. Using a regular expression to check for the presence of the hyphen or prefix.
2. Using a lookup table or dictionary to map stream IDs to their corresponding system category or event types.
3. Using a more complex conditional logic that takes into account additional factors (e.g., event type, timestamp).

It's worth noting that these alternatives may not be relevant to this specific benchmark, and the focus is on comparing the performance of two simple approaches.

Overall, this benchmark provides a good example of how to measure the performance of different conditional logic approaches in JavaScript. By understanding the options being compared, developers can gain insights into the trade-offs between approach simplicity, performance, and maintainability.

Latest run results:

Run details: (Test run date: one year ago)

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

Browser/OS: Chrome 117 on Windows

View result in a separate tab

Test name	Executions per second
isCategory First	236594800.0 Ops/sec
systemEventFirst	236822000.0 Ops/sec

Related benchmarks:

EventStore projection (version: 0)

Comparing performance of: isCategory First vs systemEventFirst

Created: one year ago by: Guest

Jump to the latest result

isCategory First

systemEventFirst

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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