You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a Nginx as load balance before the 4 node Mimir, and the nginx log show that the /api/v1/push only use about 10-20 ms, but the /prometheus/api/v1/query_range from Grafana is more than 5 sec.
Update
block_ranges_period seted to 10m is used to reduce the meomory usage, thus cause too many block, may affect the query formance.
We have 3119 target from Prometheus, each has 3600 metric, scrape_interval is 60sec.
4 Mimir node, config as below.
The Mimir use too much memory, and the query performance is bad.
We use a Nginx as load balance before the 4 node Mimir, and the nginx log show that the
/api/v1/push
only use about 10-20 ms, but the/prometheus/api/v1/query_range
from Grafana is more than 5 sec.Update
block_ranges_period
seted to 10m is used to reduce the meomory usage, thus cause too many block, may affect the query formance.The text was updated successfully, but these errors were encountered: