Skip to content

Commit 44d9fdd

Browse files
committed
Add README
1 parent 4fc8e65 commit 44d9fdd

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

README.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# JavaScript Engine Benchmark for React Native
2+
3+
## Measure Result
4+
5+
[The result will keep to be updated at Google SpreadSheets](https://docs.google.com/spreadsheets/d/1uce3WZ9IaAEUu6Owj3eXEuZb25PDi6ZcgUVV2i500S0/edit#gid=1258377944)
6+
7+
These benchmarks ran on Samsung Galaxy Note 5
8+
9+
## Benchmarks
10+
11+
### React Rendering
12+
- RenderComponentThroughput
13+
14+
The series of test cases aim to measure how many React component could be rendered within some intervals.
15+
16+
- RenderComponentThroughput 10s
17+
- RenderComponentThroughput 60s
18+
- RenderComponentThroughput 180s
19+
20+
The reason that have different interval is that to assume JIT will start to work after longer repetitive executions.
21+
22+
**Higher result is better**
23+
24+
### TTI (Time-To-Interaction)
25+
TBD
26+
27+
## How to Run the Benchmark
28+
29+
Prerequisites:
30+
31+
- Python 3
32+
- Node 8+
33+
34+
Simply to run
35+
36+
```sh
37+
python start.py
38+
```
39+
## Disclaimer
40+
41+
This project is specific to measure JS engine performance for React Native. It is not designated to do generic JS engine comparison.
42+
43+
For example, on React Native Android, we don't enable all JIT tiers on JavaScriptCore. On V8, I am currently trying to use the JIT-less mode. What I am trying to do is balancing between good enough performance, low memory usage, and small binary size. That is why to disable JIT sometimes.
44+

0 commit comments

Comments
 (0)