plugin-barman-cloud/.github/workflows
Marco Nenciarini 378c76a526
fix: resolve WAL archiving performance and memory issues (#746)
The barman-cloud plugin experienced significant performance degradation
and memory growth compared to the embedded solution. WAL archiving was
noticeably slower and memory consumption grew over time.

Root cause: The sidecar uses a read-only filesystem which prevents
Python from creating bytecode at runtime. When Python finds missing or
stale bytecode (.pyc files), it attempts to recompile on every
invocation, causing high CPU usage and memory consumption. The previous
approach pre-compiled bytecode in a separate base image, but the
bytecode was marked as stale when copied between Docker stages,
triggering runtime recompilation attempts.

This change eliminates bytecode staleness by ensuring all Python
bytecode is properly compiled in the final image before the sidecar
starts. The image is now fully distroless and based on trixie
(previously it was distroless-based but copied unnecessary files from
the build stage), reducing size from 463MB to 270MB and package count
from 188 to 35, while maintaining zero HIGH/CRITICAL vulnerabilities.

Closes #656 
Closes #711 
Closes #735

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-01-29 16:43:55 +01:00
..
ci.yml chore(deps): update dependency dagger/dagger to v0.19.10 (#730) 2026-01-15 17:40:43 +01:00
publish-docs.yml chore(deps): update actions/checkout action to v6 (#688) 2025-12-22 16:33:07 +01:00
release-please.yml chore(deps): update dependency dagger/dagger to v0.19.10 (#730) 2026-01-15 17:40:43 +01:00
release-publish.yml chore(deps): update dependency dagger/dagger to v0.19.10 (#730) 2026-01-15 17:40:43 +01:00