# Decrease processes of Grafana **URL:** \ **Category:** Configuration\ **Tags:** configuration\ **Created:** [November 13, 2024, 9:54pm UTC](https://community.grafana.com/t/decrease-processes-of-grafana/136308 "2024-11-13T21:54:25Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![ebabeshko](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@ebabeshko](https://community.grafana.com/u/ebabeshko)\ **Post date:** [November 21, 2024, 4:09am UTC](https://community.grafana.com/t/decrease-processes-of-grafana/136308/5 "2024-11-21T04:09:03Z")
May be you could try something similar: > [@I am unable to reduce the load of Grafana](https://community.grafana.com/t/i-am-unable-to-reduce-the-load-of-grafana/113289/13): > > Found what was the issue. Raised the log level with specifying -e GF\_LOG\_LEVEL=debug for the container. The log was showing: msg=“Start walking disk” messages. Apparently, by default the provisioned dashboards are checked quite often for changes. I added “updateIntervalSeconds: 600” to the dashboard yaml files and now the load is very nicely below one. I could even raise this number much higher as when I change the yaml files, I can notify Grafana about the change. Thanks for you all guys! --- _[View the full topic](https://community.grafana.com/t/decrease-processes-of-grafana/136308)._