2.8 KiB
How to optimize Gren code
When you are serving a website, there are two kinds of optimizations you want to do:
- Asset Size — How can we send as few bits as possible?
- Performance — How can those bits run as quickly as possible?
It turns out that Gren does really well on both! We have very small assets and very fast code when compared to the popular alternatives.
Okay, but how do we get those numbers?
Instructions
Step one is to compile with the --optimize
flag. This does things like shortening record field names and unboxing values.
Step two is to call uglifyjs
with a bunch of special flags. The flags unlock optimizations that are unreliable in normal JS code, but because Gren does not have side-effects, they work fine for us!
Putting those together, here is how I would optimize src/Main.gren
with two terminal commands:
gren make src/Main.gren --optimize --output=gren.js
uglifyjs gren.js --compress "pure_funcs=[F2,F3,F4,F5,F6,F7,F8,F9,A2,A3,A4,A5,A6,A7,A8,A9],pure_getters,keep_fargs=false,unsafe_comps,unsafe" | uglifyjs --mangle --output gren.min.js
After this you will have an gren.js
and a significantly smaller gren.min.js
file!
Note 1: uglifyjs
is called twice there. First to --compress
and second to --mangle
. This is necessary! Otherwise uglifyjs
will ignore our pure_funcs
flag.
Note 2: If the uglifyjs
command is not available in your terminal, you can run the command npm install uglify-js --global
to download it. You probably already have npm
from getting gren repl
working, but if not, it is bundled with nodejs.
Scripts
It is hard to remember all that, so it is probably a good idea to write a script that does it.
I would maybe want to run ./optimize.sh src/Main.gren
and get out gren.js
and gren.min.js
, so on Mac or Linux, I would make a script called optimize.sh
like this:
#!/bin/sh
set -e
js="gren.js"
min="gren.min.js"
gren make --optimize --output=$js $@
uglifyjs $js --compress "pure_funcs=[F2,F3,F4,F5,F6,F7,F8,F9,A2,A3,A4,A5,A6,A7,A8,A9],pure_getters,keep_fargs=false,unsafe_comps,unsafe" | uglifyjs --mangle --output $min
echo "Initial size: $(cat $js | wc -c) bytes ($js)"
echo "Minified size:$(cat $min | wc -c) bytes ($min)"
echo "Gzipped size: $(cat $min | gzip -c | wc -c) bytes"
It also prints out all the asset sizes for you! Your server should be configured to gzip the assets it sends, so the last line is telling you how many bytes would actually get sent to the user.
Again, the important commands are gren
and uglifyjs
which work on any platform, so it should not be too tough to do something similar on Windows.