NitroBenchmarks - GitLite

KO | EN

gitlite — search

#python #hacktoberfest #ai #golang #go #machine-learning #macos #nodejs #windows #kubernetes #awesome-list #security #openai #open-source

NitroBenchmarks

(★ 91)

Benchmarks TurboModules vs ExpoModules vs NitroModules

파일 탐색기

최종 버전 다운로드 (.zip)

- - build.gradle
  - debug.keystore
  - proguard-rules.pro
- .gitignore
- build.gradle
- gradle.properties
- gradlew
- gradlew.bat
- settings.gradle
- adaptive-icon.png
- favicon.png
- icon.png
- splash.png
- - AppDelegate.h
  - AppDelegate.mm
  - Info.plist
  - main.m
  - NitroBenchmarks-Bridging-Header.h
  - NitroBenchmarks.entitlements
  - noop-file.swift
  - PrivacyInfo.xcprivacy
  - SplashScreen.storyboard
- - project.pbxproj
- - contents.xcworkspacedata
- .gitignore
- .xcode.env
- Podfile
- Podfile.lock
- Podfile.properties.json
- - expo-module.config.json
  - index.ts
  - README.md
- - index.ts
  - MyNitroModule.podspec
  - nitro.json
  - README.md
- - MyTurboModule.podspec
  - package.json
  - README.md
- - MyCxxTurboModule.podspec
  - package.json
.gitignore
App.js
app.json
babel.config.js
package.json
README.md
tsconfig.json
yarn.lock

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Nitro Benchmarks

A react-native (or actually; Expo) app that compares react-native's **Turbo Modules** vs expo's **Expo Modules** vs @mrousavy's [**Nitro Modules**](https://github.com/mrousavy/react-native-nitro).

## About

This app specifically benchmarks the time it takes to call a synchronous function and return a result back to JS.

There are two synchronous functions per module:
- `addNumbers(a: number, b: number): number`
- `addStrings(a: string, b: string): string`

For each module, I chose the recommended language for iOS - so the TurboModule is implemented in **Objective-C**, and both the Expo Module and Nitro Module are implemented in **Swift**.

The functions are run 100.000 times after a short timeout to make sure the JS VM isn't busy with any other scheduled microtasks, and the total execution time is measured with `performance.now()`.

### About Nitro

Nitro is an upcoming library/toolkit I have been working on because I hit a lot of limitations with my libraries ([react-native-vision-camera](https://github.com/mrousavy/react-native-vision-camera), [react-native-mmkv](https://github.com/mrousavy/react-native-mmkv), [react-native-filament](https://github.com/margelo/react-native-filament), and so on).
I will use Nitro in my libraries to allow me to make them much faster than they already are, and to benefit from some fundamental differences such as it's instance-based approach. The `Frame` in VisionCamera, or `MMKV` in MMKV, or anything in Filament are all a C++ objects - I needed a better way of exposing those to JS, so I built Nitro.

I will make Nitro publicly available for everyone to build native C++, Swift or Kotlin modules with! 🔥

## Results

### iPhone 15 Pro (Release)

On my iPhone 15 Pro I got these numbers in a release build:

<table>
  <tr>
    <th></th>
    <th>ExpoModules</th>
    <th>TurboModules</th>
    <th>NitroModules</th>
  </tr>
  <tr>
    <td>100.000x <code>addNumbers(...)</code></td>
    <td>434.85</td>
    <td>115.86ms</td>
    <td><b>7.27ms</b></td>
  </tr>
  <tr>
    <td>100.000x <code>addStrings(...)</code></td>
    <td>429.53ms</td>
    <td>179.02ms</td>
    <td><b>29.94ms</b></td>
  </tr>
</table>

- For `addNumbers(...)`, Nitro Modules is **59x as fast as ExpoModules**, and **15x as fast as TurboModules** 🔥
- For `addStrings(...)`, Nitro Modules is **13x as fast as ExpoModules**, and **5x as fast as TurboModules** 🔥

---

### Mac Studio (Apple M1 Max)

On my Mac Studio (Apple M1 Max, 32GB RAM), I got these numbers in a release build ("designed for iPad"):

<table>
  <tr>
    <th></th>
    <th>ExpoModules</th>
    <th>TurboModules</th>
    <th>NitroModules</th>
  </tr>
  <tr>
    <td>100.000x <code>addNumbers(...)</code></td>
    <td>764.31ms</td>
    <td>195.12ms</td>
    <td><b>42.32ms</b></td>
  </tr>
  <tr>
    <td>100.000x <code>addStrings(...)</code></td>
    <td>773.00ms</td>
    <td>308.65ms</td>
    <td><b>138.43ms</b></td>
  </tr>
</table>

## NitroModules: Swift vs C++

In addition to platform-specific languages, NitroModules can be written in C++, a cross-platform language.
C++ is a lot faster than platform-specific languages like Swift or Kotlin:

<table>
  <tr>
    <th></th>
    <th>NitroModules Swift</th>
    <th>NitroModules C++</th>
  </tr>
  <tr>
    <td>100.000x <code>addNumbers(...)</code></td>
    <td>8.21ms</td>
    <td><b>6.33ms</b></td>
  </tr>
  <tr>
    <td>100.000x <code>addStrings(...)</code></td>
    <td>68.20ms</td>
    <td><b>12.99ms</b></td>
  </tr>
</table>

## C++ TurboModule vs C++ NitroModule

When using C++ only, Nitro still has a more direct binding to native.
On an iPhone Air, these are the results:

<table>
  <tr>
    <th></th>
    <th>TurboModules C++</th>
    <th>NitroModules C++</th>
  </tr>
  <tr>
    <td>100.000x <code>addNumbers(...)</code></td>
    <td>13.97ms</td>
    <td><b>4.32ms</b></td>
  </tr>
  <tr>
    <td>100.000x <code>addStrings(...)</code></td>
    <td>17.47ms</td>
    <td><b>8.93ms</b></td>
  </tr>
</table>

## Real-world

Note that these are just very specific benchmarks. They profile JS <-> Native function execution time (call, argument parsing, and result argument conversion).
**In an actual real world app, performance may vary.**

## Correctness

Note: I put these benchmarks together in ~1 hour. My focus is on making [Nitro Modules](https://github.com/mrousavy/react-native-nitro) as fast as possible, but also as powerful as possible, so this is where my time is dedicated at.
**If I made any mistakes in the benchmark, please let me know so I can update it asap!**

I don't intend to put Turbo or Expo modules in bad light here, they are insanely cool tools to build native modules.