Spring Native + Cloud Run : cold-start 18, RAM 3, facture à 0 FCFA
The article discusses the challenges of using Spring Native with Cloud Run, particularly focusing on cold-start times and associated costs. It highlights the significant delays experienced during application startup and the financial implications for developers. The author shares insights from their experience, emphasizing the importance of optimizing performance to avoid excessive charges.
- ▪Cold-start times for Spring Boot on Cloud Run can reach up to 3.8 seconds, leading to increased costs.
- ▪Each cold-start consumes vCPU and RAM resources, which are billed regardless of transaction success.
- ▪Optimizing application startup times can significantly reduce resource consumption and costs.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 972716) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } BANGA Posted on May 26 • Originally published at ban.ga Spring Native + Cloud Run : cold-start 18, RAM 3, facture à 0 FCFA #java #spring #graalvm #gcp Cet article est la version condensée de mon retour d'expérience complet sur ban.ga — config Maven -Pnative détaillée, registrar RuntimeHintsRegistrar pour la console H2, pipeline PowerShell de 200 lignes, et chaque piège décortiqué.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
