All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

How Kestra Improved Orchestrator Performance Across 14 Releases: A Year of Performance Engineering

By

Kestra

2d ago· 19 min readenInsight

Summary

Kestra's engineering team details their year-long performance engineering journey across releases 0.19 to 1.3, treating performance as an ongoing discipline rather than a one-time project. The article covers systematic improvements through benchmarks, profiling, database optimization, and iterative code refinement to make the orchestrator faster, leaner, and more scalable.

Key quotes

· 3 pulled
Performance is not a one-shot project. It is a discipline — measured release after release, paid for in benchmarks, profiler flame graphs, late-night database explain plans, and the patience of engineers willing to revisit 'good enough' code and ask: can we do better?
Over the past year, the Kestra engineering team has shipped performance improvements in every single release between 0.19 and 1.3.
The cumulative impact
Snippet from the RSS feed
Performance Engineering at Kestra: From 0.19 to 1.3 How we made the orchestrator faster, leaner, and more scalable, one release at a time. By Loïc Mathieu, Lead Sotware Engineer, @Kestra Performance …

You might also wanna read