Loki: Increase (query/search) performance for the Docker / single binary?

Grafana Loki
,
1

Hi,

Then running the “docker-compose” version of Loki, all queries are running on a single CPU-core, which is inefficient especially then you have multiple cores available (and go is really good at doing parallel tasks) .

I found this article, but it’s for running loki in k8s.
https://localhost:3000/t/how-to-improve-loki-performance/42800
And I guess most bigger installations has moved to k8s already.

I tried to add some configs from the Slack channel, but that had no effect on parallelism AFAICT. But from the post above, I interpret that there need to be more frontend_workers too?

query_range:
  align_queries_with_step: true
  max_retries: 10
  split_queries_by_interval: 15m
  split_queries_by_day: true
  parallelise_shardable_queries: true
  cache_results: true
  results_cache:
    cache:
      redis:
        endpoint: loki:6379
        expiration: 86400s
        db: 1
        timeout: 60s

If possible, How would a single binary config for more parallel “search workers” look like?

1 Like
2

To illustrate this, this happens when I perform a query in Loki/Grafana then I do a query+filter like {label=somelabel} |= “something_I_search_for”

docker-loki
docker-loki1764×1594 669 KB

(second row shows the thread going 100% while the others have basically no load)

1 Like
3

Hi, did you solve the issue yet? I am running loki in local build mode by following the doker compose design as well.

4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.