You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By looking into the content, the dominant factor is the following file in non stable ones.
$ du -h prometheus-k8s_edge/venv/grpc/_cython/cygrpc.cpython-38-x86_64-linux-gnu.so
297M prometheus-k8s_edge/venv/grpc/_cython/cygrpc.cpython-38-x86_64-linux-gnu.so
After looking up the internet (grpc/grpc#21958), there was a hint that the binary may contain the debug info in it. And indeed, stripping the debug info by hand trimmed down the size significantly.
$ strip --strip-debug prometheus-k8s_edge/venv/grpc/_cython/cygrpc.cpython-38-x86_64-linux-gnu.so
$ du -h prometheus-k8s_edge/venv/grpc/_cython/cygrpc.cpython-38-x86_64-linux-gnu.so
14M prometheus-k8s_edge/venv/grpc/_cython/cygrpc.cpython-38-x86_64-linux-gnu.so
Not so sure how to fix the situation properly in this charm though.
To Reproduce
$ juju download --channel 1.0/stable prometheus-k8s
Base "[email protected]" is not supported for charm "prometheus-k8s", trying base "[email protected]"
Fetching charm "prometheus-k8s" revision 129 using "1.0/stable" channel and base "amd64/ubuntu/20.04"
Install the "prometheus-k8s" charm with:
juju deploy ./prometheus-k8s_r129.charm
$ unzip -d prometheus-k8s_stable ./prometheus-k8s_r129.charm
$ juju download --channel 1.0/edge prometheus-k8s
Base "[email protected]" is not supported for charm "prometheus-k8s", trying base "[email protected]"
Fetching charm "prometheus-k8s" revision 146 using "1.0/edge" channel and base "amd64/ubuntu/20.04"
Install the "prometheus-k8s" charm with:
juju deploy ./prometheus-k8s_r146.charm
$ unzip -d prometheus-k8s_edge ./prometheus-k8s_r146.charm
$ du -sh prometheus-k8s_*/
381M prometheus-k8s_edge/
36M prometheus-k8s_stable/
nobuto-m
changed the title
The charm size got 10x bigger than before
The charm size got 10x bigger due to cygrpc.cpython-38-x86_64-linux-gnu.so with debug symbols
Nov 7, 2023
Most likely this is related to charm tracing support introduction in the prometheus charm which uses gRPC to communicate with tempo. We're investigating switching to another protocol in canonical/tempo-k8s-operator#53.
Bug Description
As you can see blow, the charm size got 10x bigger in candidate/beta/edge compared to the stable one.
By looking into the content, the dominant factor is the following file in non stable ones.
After looking up the internet (grpc/grpc#21958), there was a hint that the binary may contain the debug info in it. And indeed, stripping the debug info by hand trimmed down the size significantly.
Not so sure how to fix the situation properly in this charm though.
To Reproduce
Environment
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: