You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the API memory leak is not fully resolved, we want to benchmark and watch performance as well as keep this issue open for further work toward complete resolution.
This Issue uses the original reproduction with the new benchmarks.
Background
Originally reported by @zygopleural here:
Web memory leak resolved and API memory leak mitigated via:
Because the API memory leak is not fully resolved, we want to benchmark and watch performance as well as keep this issue open for further work toward complete resolution.
This Issue uses the original reproduction with the new benchmarks.
related benchmark issue #4356
Expected behaviour
yarn redwood test
should use ~ same heap size for each test unless the user has specifically done something wrong.i.e. the heap size should not increase with each consecutive test or run (i.e. leak)
What currently happens
rw test web
:The heap size is stable
rw test api
:Even after mitigation in #4096 the heap size increases along with quantity of tests
Steps to reproduce
Option 1: Clone the Reproduction Repo
Option 2. Create new app and run commands
1. Creat App
yarn create redwood-app --typescript test
2. Add some models to
./api/db/schema.prisma
Excuse the silly models, just something quick to generate tests.
3. Generate some tests
4. Run tests
yarn redwood test --logHeapUsage
Benchmarks as of v0.44
Initial test (watch mode)
Second Run (watch
mode)
Third Run (watch mode)
The text was updated successfully, but these errors were encountered: