search

kokoye2007 / waitzar

Automatically exported from code.google.com/p/waitzar
Other
0 stars 1 forks source link

Executable Size #106

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Version 1.7 of WZ was 0.63 MB. 1.8 looks to be much bigger. 

Part of the problem is boost:

Current (pre-1.8) build:
  1.43 MB in release mode

After removing the spirit & boost libraries
  1.16 MB in release mode

Total savings ~276 KB. We could replace this with the ~188 KB V8 engine,
and gain at least ~88 KB (plus the ability to use JavaScript anywhere).

Beyond that, I'm not sure what's taking up so much space. The fonts are
certainly sizeable, and we might consider using TTFs if quality is good and
memory use doesn't explode. But I like the PNG fonts' speed. 

Anyway, 1.8 will be somewhat big; there's no avoiding it. At least the
total archive size should be smaller (with the PDF user's guide). But 1.9
should focus on reducing the executable's size, in addition to the usual
minor features and bug fixes (and romanization upgrade).

Original issue reported on code.google.com by seth.h...@gmail.com on 9 Mar 2010 at 8:09

GoogleCodeExporter commented 9 years ago 
Note that we can get the EXE down to 432 KB using UPX. 

From a few simple tests:
  1) Nothing seems broken.
  2) Startup time is not really affected.

Command line:
  upx.exe --best WaitZar.exe

We might consider doing this for release mode, and having users test with this. 
I see
no benefit to keeping the EXE un-compressed, and 432 KB is about the size of 
release 1.6.

upx.exe --best --ultra-brute WaitZar.exe
...gets the file size down to 374 KB, which is about the size of release 1.5. It
takes forever, but why not do it on release?

Original comment by seth.h...@gmail.com on 9 Mar 2010 at 8:28

GoogleCodeExporter commented 9 years ago 
....

Seriously, the ability to reduce an executable by 75% of its total size with no
noticeable lag on startup is just amazing. Why AREN'T we using UPX?

....

Original comment by seth.h...@gmail.com on 9 Mar 2010 at 8:30

GoogleCodeExporter commented 9 years ago 
Ok, I've built and shipped several demos with UPX and no-one's found any obvious
bugs. From now on, we use UPX.

Original comment by seth.h...@gmail.com on 18 Mar 2010 at 5:38