Performance tests (benchmarks) is required #632
bekliev
started this conversation in
4. General
Replies: 1 comment 1 reply
-
You have to think about what is important for the library in terms of performance. For most JavaScript libraries, that means how long it takes to completely initialise and how performant DOM operations are. The first would involve both Alpine running the DOM walks as well as any initial DOM operations for bindings, visibility and actual node presence. You could even micro-benchmark / unit-benchmark things like the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
A while ago I've created a couple of PRs:
But there's a problem with determining of usefulness of these PRs, cause at the moment we don't have ability to compare performance BEFORE and AFTER changes in those PRs.
I've made some isolated tests for the approach I've implemented in those PRs, but it doesn't show clearly how it will affect in real application in runtime.
I suggest to create benchmarks specifically for this library
I've never done benchmarks for libraries but only small performance tests.
And I even cannot imagine how the benchmark for this library should look like.
How many cases should be covered and etc.
Let's find out together.
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions