Open karmacoma-eth opened 1 month ago
A few more ideas:
Improvements since first post:
Before (forge 0.2.0 (3e3b30c 2024-08-15T00:19:22.864621297Z))
26M ./anvil
26M ./anvil.stripped
50M ./cast
50M ./cast.stripped
35M ./chisel
35M ./chisel.stripped
76M ./forge
76M ./forge.stripped
After (forge 0.2.0 (1d2379a 2024-09-22T00:23:17.631577994Z))
22M ./anvil
20M ./anvil.stripped
41M ./cast
36M ./cast.stripped
29M ./chisel
25M ./chisel.stripped
60M ./forge
54M ./forge.stripped
du -sh ~/.config/.foundry/bin/*
rm -f ./*.stripped; for f in ./*; do strip $f -o $f.stripped; done
Compare with February version (forge 0.2.0 (2cb8757 2024-02-03T00:16:46.961268899Z))
20M ./anvil
18M ./anvil.stripped
34M ./cast
31M ./cast.stripped
23M ./chisel
21M ./chisel.stripped
46M ./forge
42M ./forge.stripped
Note that the February version doesn't include much of alloy, has revm 3 which is pre-handlers, pre-eof, pre-soldeer etc; a ton less cheatcodes, config options... So some size increase is to be expected, but we can still do better
Component
Forge, Cast, Anvil, Chisel
Describe the feature you would like
on macOS, with last week's foundry, I noticed that the foundry binaries are quite large:
after foundryup, some of them got even bigger:
This also contributes significantly to the size of docker images that install foundry. Thanks!
Additional context
No response