Code performance after compression (UglifyJS vs Closure vs JSMin vs JSPacker vs YUI Compressor

[Simo Moujami]

Code compression is important but browse caching makes it a one-time concern. Code performance after compression on the other hand is a constant factor, whether you're loading a web page or simply invoking a function. If code performance is important to you, then check out these benchmarks:

http://jsperf.com/testing-code-performance-by-compression-type

In this example, I've used DWR's engine.js, compressed it using various compressors, then compared code execution. 

The results suggest Google Closure Compiler  (Advanced mode) generates code that is potentially faster than the original code (pink) and is by far the fastest compressor.

Check out the link above for an interactive graph of to run the same tests locally. 

[Alex Objelean]

Thank you Simo for sharing this. Very interesting information.

Cheers,
Alex

--
You received this message because you are subscribed to the Google Groups "wro4j" group.
To view this discussion on the web visit https://groups.google.com/d/msg/wro4j/-/Z2HrAvptOiYJ.
To post to this group, send email to wr...@googlegroups.com.
To unsubscribe from this group, send email to wro4j+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wro4j?hl=en.

[Simo Moujami]

You're welcome :) 

Makes a point about what's worth supporting in the future. Hopefully the next release (1.6.1?) will bring support back to google closure.

Thanks for your hard work and for this great plugin!

[nmcc...@gmail.com]

AWESOME! thank you!

[varu...@gmail.com]

Precisely what I wanted!

Thank you so much!

Regards,

Varun Shringarpure

[jothi...@gmail.com]

the mentioned URL http://jsperf.com/testing-code-performance-by-compression-type throws 404 page. Can you update the correct page plz.