What about jide.js performance?

The other day, I noticed that there is a nice and simple benchmark for toolkits like jide.js: jashkenas’s Ember/Backbone.

So, since the next release of jide.js is supposed to introduce massive performance improvements, I thought it might be a good idea to see how it holds up against this benchmark. I used a modified version from vue.js which seems to include a few more nice frameworks.

Please note that these kinds of benchmarks are rather useless. This particular benchmark can be solved in a many ways when using jide.js. I only implemented two of those but there are other ways to do it, some of which might be even faster.

The first jide.js benchmark uses a separate Box class which contains the properties. This helps to circumvent native events on jidejs/ui/Component. Anyway, here are my results (on an Intel Core i5-3317U with 1.70GHz and 8GB RAM – it’s an Ultrabook – using Chrome):

jide.js

11.24 ms per loop

jide.js (without separate class)

12.02 ms per loop

Backbone

45.04 ms per loop

Ember+HTMLBars

17.53 ms per loop

React

25.16 ms per loop

Vue

16.34 ms per loop

nothing

11.32 ms per loop

I waited a couple of seconds and used the smallest number that showed up. Naturally, I’m quite happy with the result. If you want to, take a look at it.

Again, I want to point out that these Benchmarks are useless. Especially ones like this one. Yes, jide.js is (will be) fast at updating lots of DOM nodes but in a typical application, you’ll not do that as often.

What I find much more interesting is that all of jide.js that is required for this benchmark weighs in at only 16.4KB (vue.js has 13.2KB) minified and gzip’d. That’s pretty small for what you get.