reboot superset

[charlieLin552]

After the superset is started, dashboards and charts are automatically queried. As a result, junk SQL statements are encountered within a period of time after the superset is started, which causes the CPU usage of the clickhouse to skyrocket. What can I do to avoid automatically querying dashboards or charts? and I started the celery boot and celery worker.

[dosubot[bot]]

I found a similar unsolved discussion on this topic: Async Queries in Dashboards & Charts ^[1]. Unfortunately, there was no solution found in the comments of a related closed issue ^[2].

To address the issue of automatic querying of dashboards and charts upon startup, you might consider customizing the startup behavior of Apache Superset. One approach is to adjust the concurrency level of the Celery workers to manage CPU usage. You can set the CELERYD_CONCURRENCY environment variable to a lower value to reduce CPU usage:

export CELERYD_CONCURRENCY=1

Then start the worker with the updated concurrency setting:

celery --app=superset.tasks.celery_app:app worker -O fair -l INFO --concurrency=${CELERYD_CONCURRENCY:-2}

This will help in managing CPU usage by limiting the number of concurrent tasks processed by Celery workers ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}