feat: Measure performance of resolution and shader compilation#1441
feat: Measure performance of resolution and shader compilation#1441
Conversation
|
pkg.pr.new packages benchmark commit |
|
I get an error when running the tests, any ideas? 
|
Yes, the dev server has to be running during the test, for assets 👀 |
Ofc, my bad |
reczkok
left a comment
reczkok
left a comment
There was a problem hiding this comment.
Amazing addition! No more manual clicking 🙇♂️
apps/typegpu-docs/src/content/examples/simulation/fluid-with-atomics/index.ts
Show resolved
Hide resolved
aleksanderkatan
left a comment
aleksanderkatan
left a comment
There was a problem hiding this comment.
Great job, super useful!
apps/typegpu-docs/src/content/examples/simulation/fluid-with-atomics/index.ts
Show resolved
Hide resolved
| */ | ||
| const timeout = 120 * 1000; | ||
|
|
||
| const iterations = 10; |
There was a problem hiding this comment.
Could we make it a little smaller, or could we make the number of iterations passable via the command line?
| * The amount of time after Vitest decides that the test | ||
| * has gone rogue. Adjust as necessary. | ||
| */ | ||
| const timeout = 120 * 1000; |
There was a problem hiding this comment.
I think this timeout may be a little to close to how long the test actually takes, it actually timed out on me once even though there was no lag nor wait for camera permission. Can we also make it depend on the number of iterations?
3 participants
Screen.Recording.2025-07-03.at.19.42.21.mov
Benchmark results as generated HTML & JSON: