-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance #6
Comments
It is just string concatenation. Simple and quick operation with a small number of objects. |
Sure, but even so, calling a bunch of |
So far we did not have critical performance issues. But I guess there is a small pay-off especially when using |
I did test if it would be possible to create a cache based on a stringified configuration object on each call. But looks like |
I was looking at this lib and has the same concern. Maybe someone can put a simple demo together and measure the perf? |
In the meantime I created a new plugin for us, which is able to reduce the amount of recalculation and also caches hyphenation. See https://www.npmjs.com/package/@verstaerker/vue-bem |
Unfortunately (for me) I have to admit, that additional test showed that, while my internal code performed faster, the overall rendering time eventually is higher (we are talking about higher two digit milliseconds here). As I currently see it this is due the fact how Vue handles directives. So far I was not able to get it down to the speed that the vue-bem-cn plugin offers... I actually wanted to also post some testing results, but I was not able to make an extensive comparison yet. |
We're binding our classes to a
b()
method. Doesn't that mean that theb()
method gets processed everytime the template re-renders?What is the performance hit?
The text was updated successfully, but these errors were encountered: