Open
Description
Test Report:
| Framework | Test Case | Time (μs) |
|---|---|---|
| reactter | avoidablePropagation (success) | 1246122 |
| reactter | broadPropagation (success) | 4989682 |
| reactter | deepPropagation (success) | 3999993 |
| reactter | diamond (fail) | 14030768 |
| reactter | mux (success) | 1022652 |
| reactter | repeatedObservers (success) | 9744089 |
| reactter | triangle (success) | 4518305 |
| reactter | unstable (success) | 7640850 |
| reactter | molBench | 5896885 |
| reactter | create_signals | 13341 |
| reactter | comp_0to1 | 13681 |
| reactter | comp_1to1 | 99563 |
| reactter | comp_2to1 | 72373 |
| reactter | comp_4to1 | 85231 |
| reactter | comp_1000to1 | 59322 |
| reactter | comp_1to2 | 66888 |
| reactter | comp_1to4 | 99179 |
| reactter | comp_1to8 | 116368 |
| reactter | comp_1to1000 | 47899 |
Test file: https://github.com/medz/dart-reactivity-benchmark/blob/main/frameworks/reactter.dart
Hi, your library API is well designed👍. But I am benchmarking reactivity in Dart ecosystem, and I found that reactter is running slowly, which may be caused by the following problems:
-
Extensive use of Set/List leads to increased memory
-
My integration code is implemented incorrectly.
It is worth noting that when my test runs to 1 to 1000 tests, it cannot continue to run and the program has been locked.
reactter performs well in small scale, but it will be very slow when encountering a scale of more than 100. In addition, reactter has serious memory leak problems.