mdgriffith/elm-optimize-level-2
1
1
Fork 0
mirror of https://github.com/mdgriffith/elm-optimize-level-2.git synced 2024-11-29 12:46:32 +03:00
Code Issues Packages Projects Releases Wiki Activity

update name in other places

Browse Source
This commit is contained in:
mdgriffith 2020-08-24 07:56:01 -04:00
parent 1c98cbebb1
commit 6d186c5261
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
notes/minification.md
View File

@ -2,7 +2,7 @@
We're basically following the same protocol as [described on the Elm Guide.](https://guide.elm-lang.org/optimization/asset_size.html) We use Terser, which is just an actively maintained fork of Uglify. We're basically following the same protocol as [described on the Elm Guide.](https://guide.elm-lang.org/optimization/asset_size.html) We use Terser, which is just an actively maintained fork of Uglify.
After installing `elm-optimize-more`, After installing `elm-optimize-level-2`,
Install a minifier like [`Terser`](https://www.npmjs.com/package/terser). Install a minifier like [`Terser`](https://www.npmjs.com/package/terser).
@ -13,7 +13,7 @@ npm install -g terser
Then, you'll want to run these commands to minify and gzip your code before deploying. Then, you'll want to run these commands to minify and gzip your code before deploying.
```bash ```bash
elm-optimize-more Main.elm --output=app.js elm-optimize-level-2 Main.elm --output=app.js
terser app.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' | terser --mangle --output=app.min.js terser app.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' | terser --mangle --output=app.min.js
gzip --keep --force app.min.js gzip --keep --force app.min.js

14
notes/transformations.md
View File

@ -1,6 +1,6 @@
# Overview of Transformations # Overview of Transformations
This is an overview of the transformations for `elm-optimize-more`. This is an overview of the transformations for `elm-optimize-level-2`.
Not all of them made the cut, but seeing that a transformation is not as effective as initially thought is really good information. Not all of them made the cut, but seeing that a transformation is not as effective as initially thought is really good information.
@ -51,7 +51,7 @@ MyFunction_fn(one two)
## Results Summary ## Results Summary
- Included in `elm-optimize-more` tool\*\* - Included in `elm-optimize-level-2` tool\*\*
- Potentially large positive effect on speed - Potentially large positive effect on speed
- Likley small but positive effect on asset size - Likley small but positive effect on asset size
@ -177,7 +177,7 @@ There may be a nice trade-off here of using `InlineMode.UsingConsFunc`, but only
## Results Summary ## Results Summary
- Not included in the elm-optimize-more tool because it was hard to find a benchmark that reported numbers to justify it. - Not included in the elm-optimize-level-2 tool because it was hard to find a benchmark that reported numbers to justify it.
- Though maybe we just need to be better at benchmarking it. - Though maybe we just need to be better at benchmarking it.
# Object Update # Object Update
@ -258,7 +258,7 @@ Or we can use the spread operator inline:
## Result Summary ## Result Summary
- Not included in elm-optimize-more tool - Not included in elm-optimize-level-2 tool
- Again, all of these tricks rely on either the spread operator or `Object.assign`, both of which are not supported in IE. - Again, all of these tricks rely on either the spread operator or `Object.assign`, both of which are not supported in IE.
- The most promising approach was inlining the call completely with `{...old, field: newValue}`. - The most promising approach was inlining the call completely with `{...old, field: newValue}`.
- Gave a `501%` boost in chrome! - Gave a `501%` boost in chrome!
@ -302,11 +302,11 @@ If Elm's `==` is applied to any primitive such as:
Then we can inline the definition directly as JS strict equality: `===`. Then we can inline the definition directly as JS strict equality: `===`.
Right now `elm-optimize-more` will infer if something is a primitive if a literal is used. Right now `elm-optimize-level-2` will infer if something is a primitive if a literal is used.
## Results Summary ## Results Summary
- Included in `elm-optimize-more` tool. - Included in `elm-optimize-level-2` tool.
- Looks to have the some impact on code that does a lot of equality comparisons, like parsing. - Looks to have the some impact on code that does a lot of equality comparisons, like parsing.
The `_Utils_eq` function is very likely deoptimized because it can take _any_ two values and either do a reference check, or do structural equality, which we also know takes a while. The `_Utils_eq` function is very likely deoptimized because it can take _any_ two values and either do a reference check, or do structural equality, which we also know takes a while.
@ -355,7 +355,7 @@ This is still a benefit because the minified code is what ultimately needs to be
## Results Summary ## Results Summary
- Not included in the `elm-optimize-more` tool - Not included in the `elm-optimize-level-2` tool
- Comes with the caveat that the [code will not work on IE](https://caniuse.com/#feat=arrow-functions) - Comes with the caveat that the [code will not work on IE](https://caniuse.com/#feat=arrow-functions)
We weren't able to pin down a benchmark where this reported a benefit in the numbers, though likely to explore this we need (1) A larger codebase, and (2) We weren't able to pin down a benchmark where this reported a benefit in the numbers, though likely to explore this we need (1) A larger codebase, and (2)