Skip to main content

Comparison of (2) Javascript compression tools

I use more and more javascript files in my web applications and their size is slowly becoming a problem, especially among those users who connect infrequently and are on slow links.
So I have eventually decided to google the internet for javascript compression tools.
What I need though is not a generic web-based javascript compression tool, but one that I can easily incorporate in my ant build scripts.

In the end there were only two candidates left: ShrinkSafe from dojotoolkit and jsjuicer. So I tried both of them against prototype.js which I happen to use on many projects and is actually quite large (96K!).

The results is the following:
unicoletti@ziggy ~/bin $ll prototype*
-rw-r--r-- 1 unicoletti unicoletti 71758 2007-05-31 17:27 prototype-jsjuicer.js
-rw-r--r-- 1 unicoletti unicoletti 68004 2007-05-31 17:27 prototype-shrinksafe.js
-rw-r--r-- 1 unicoletti unicoletti 96046 2007-05-31 17:26 prototype.js

And the winner is: ShrinkSafe, even though it a little slower and more hungry on resources, because to its Java nature.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …