Artem Fetishev 6ab8c9cd4d lib/storage: do not search global index when per-day index is enabled (#11697)
When vmstorage has per-day index enabled (-disablePerDayIndex=false,
this the default behavior) it writes two indexes anyway: global and per-day. This
was done to make long time range queries faster. I.e. queries with short
time ranges indeed search per-day index, but the time range becomes more than an
month, then vmstorage switches to global index search.
    
This PR disables this behavior. The main reason is the upcoming feature
of disabling global index (see
https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11196). This
feature assumes that only one index type is used at any given time, meaning that
if per-day index is enabled (still the default behavior) then global index
is not used at all: no global index entries created and searched.
    
But this commit seems to be useful on its own because the benchmarks
show that there are no performance gains in searching global index for longer time
ranges when the churn rate is HIGH (k8s use case). However, searching global
index does improve search performance when the churn rate is low or absent (iot use
case). But in this case it is recommended to disable per-day index (see
https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#index-tuning-for-low-churn-rate).

Signed-off-by: Artem Fetishev <rtm@victoriametrics.com>
2026-10-05 16:31:28 +02:00
2025-06-11 13:54:16 +02:00
2026-09-29 10:19:18 +02:00
2026-09-30 20:53:08 +02:00
2025-06-30 17:01:05 +02:00
2024-08-29 10:35:36 +02:00
2026-09-30 20:53:08 +02:00
2026-09-30 20:53:08 +02:00
2026-08-20 10:17:48 +02:00

VictoriaMetrics

Latest Release Docker Pulls Build Status License Join Slack X Reddit

VictoriaMetrics logo

VictoriaMetrics is a fast, cost-effective, and scalable solution for monitoring and managing time series data. It delivers high performance and reliability, making it an ideal choice for businesses of all sizes.

Here are some resources and information about VictoriaMetrics:

Yes, we open-source both the single-node VictoriaMetrics and the cluster version.

Prominent features

VictoriaMetrics is optimized for timeseries data, even when old time series are constantly replaced by new ones at a high rate, it offers a lot of features:

Enterprise version

In addition, the Enterprise version includes extra features:

  • Anomaly detection: Automation and simplification of your alerting rules, covering complex anomalies found in metrics data.
  • Backup automation: Automates regular backup procedures.
  • Multiple retentions: Reducing storage costs by specifying different retentions for different datasets.
  • Downsampling: Reducing storage costs and increasing performance for queries over historical data.
  • Stable releases with long-term support lines (LTS).
  • Comprehensive support: First-class consulting, feature requests and technical support provided by the core VictoriaMetrics dev team.
  • Many other features, which you can read about on the Enterprise page.

Contact us if you need enterprise support for VictoriaMetrics. Or you can request a free trial license here, downloaded Enterprise binaries are available at Github Releases.

We strictly apply security measures in everything we do. VictoriaMetrics has achieved security certifications for Database Software Development and Software-Based Monitoring Services. See Security page for more details.

Benchmarks

Some good benchmarks VictoriaMetrics achieved:

Community and contributions

Feel free to ask any questions regarding VictoriaMetrics:

If you like VictoriaMetrics and want to contribute, then please read these docs.

The provided ZIP file contains three folders with different logo orientations. Each folder includes the following file types:

  • JPEG: Preview files
  • PNG: Preview files with transparent background
  • AI: Adobe Illustrator files

VictoriaMetrics Logo Usage Guidelines

Font

  • Font Used: Lato Black
  • Download here: Lato Font

Color Palette

Logo Usage Rules

  • Only use the Lato Black font as specified.
  • Maintain sufficient clear space around the logo for visibility.
  • Do not modify the spacing, alignment, or positioning of design elements.
  • You may resize the logo as needed, but ensure all proportions remain intact.

Thank you for your cooperation!

Languages
Go 87.7%
TypeScript 9.2%
SCSS 1.5%
Makefile 0.9%
Shell 0.5%