Prometheus 2.53 Released: Lower Memory and an LTS Line
Prometheus 2.53 changed the Go garbage-collection default to greatly reduce memory usage, added a query_offset option for remote-write resilience, and optimized querying with regexp matchers.
Historical Archive. This article documents an event from 2024 and is preserved with its original date for reference. It is not current news, and details may have changed since publication.
What happened
Prometheus 2.53.0 was released on June 16, 2024, according to the official GitHub release notes. It became the basis of a long-term-support line for the 2.x series, giving operators a stable version to run before the major 3.0 transition later in the year.
Lower memory usage
The headline change was to the default value of GOGC, the Go runtime control governing the trade-off between excess memory use and CPU usage. The maintainers found that Prometheus operates with minimal additional CPU usage but greatly reduced memory by adjusting the Go default from 100 to 75, an efficiency win that benefits the many large Prometheus deployments.
Rule resilience
Prometheus 2.53 added a new query_offset option for each rule group via the rule-group configuration file, along with a rule_query_offset global option, to provide more resilience against remote-write delays. It also changed alert restoration to execute a single query instead of one per alert within a rule, reducing load when restoring alerts, and added a metric to measure how long restoring a rule group takes.
Query and OTLP improvements
The release optimised querying with regexp matchers in the time-series database, improved remote-write format translation performance for OpenTelemetry data by using label-set hashes for metric identifiers instead of string-based ones, and let queries with heavy regex matches be cancelled so they do not use up CPU. It also fixed head stats and hooks when replaying a corrupted snapshot.
Why it mattered
Prometheus 2.53 delivered a meaningful efficiency improvement for free through the GOGC change, cutting memory usage across deployments. As an LTS release it also gave conservative operators a well-supported stopping point on the 2.x line before deciding when to move to the breaking 3.0 release.
Related on Skillo
See also: Prometheus 2.40 and native histograms, Prometheus 3.0's new UI and UTF-8.
Sources
Published date reflects the original event date (2024-06-16). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.
Written by
Skillo Staff
0 Comments
Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.