Binary size issue.
29 views
Skip to first unread message
Alexandru Barborica
Nov 30, 2019, 9:16:00 AM11/30/19
to envoy-users
Hello, I just have a quick question, building envoy with "
bazel build -c opt //source/exe:envoy-static" results in a 1.3GB binary. I'm currently looking into deploying envoy sidecars and 1.3GB seems a bit too much to cram in a container. If I compile with the sizeopt argument will that get me down to what I hear people reporting like 8 14 20mb? Or is it a problem with my build environment?
Ben Plotnick
Nov 30, 2019, 1:51:42 PM11/30/19
to Alexandru Barborica, envoy-users
If you use the version that has the symbols stripped, it should be much smaller:
On Sat, Nov 30, 2019 at 6:16 AM Alexandru Barborica <alexba...@gmail.com> wrote:
Hello, I just have a quick question, building envoy with "bazel build -c opt //source/exe:envoy-static" results in a 1.3GB binary. I'm currently looking into deploying envoy sidecars and 1.3GB seems a bit too much to cram in a container. If I compile with the sizeopt argument will that get me down to what I hear people reporting like 8 14 20mb? Or is it a problem with my build environment?
--
You received this message because you are subscribed to the Google Groups "envoy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to envoy-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/envoy-users/7c7a2bad-5a54-48d5-b90c-8fa9d6837de8%40googlegroups.com.
Tony Allen
Nov 30, 2019, 4:09:23 PM11/30/19
to Ben Plotnick, Alexandru Barborica, envoy-users
In addition to making sure you use the stripped binary, you can disable any extensions you're not using so they aren't compiled:
To view this discussion on the web visit https://groups.google.com/d/msgid/envoy-users/CAAE4cEEF6h2K5yJ%3DZL0ptN5MLNAsdU844UBR%2BSMQTiAK9EWcpA%40mail.gmail.com.
--
Tony Allen Software Engineer |
 |
Reply all
Reply to author
Forward
0 new messages