Is it normal for a brand new airflow installation to take multiple seconds to run a simple DAG?

[albertjmr]

I recently deployed airflow to a company managed k8s cluster using this chart!

Everything is running fine and I can already run some dummy DAGs, etc. I'm mostly using the default values that come up with the community chart (using CeleryExecutor).

However, I've noticed that even a simple DAG takes many seconds to execute, tasks take always 1-2s in the queuing step for instance.

Here is the gantt chart for a simple DAG I created based on some examples online, as you can see, it takes over 1s to queue each task and the task themselves take seconds to execute too (even though they only involve 1-2 lines of python):

The code of this DAG is as follows:

from datetime import datetime
from random import randint

from airflow import DAG
from airflow.operators.bash import BashOperator
from airflow.operators.python import BranchPythonOperator, PythonOperator


def _choosing_best_model(ti):
    accuracies = ti.xcom_pull(
        task_ids=["training_model_A", "training_model_B", "training_model_C"]
    )

    if max(accuracies) > 8:
        return "accurate"

    return "inaccurate"


def _training_model():
    # return an integer between 1 - 10
    return randint(1, 10)


with DAG(
    "dummy_dag",
    start_date=datetime(2021, 1, 1),
    schedule_interval="@daily",
    catchup=False,
) as dag:
    training_model_tasks = [
        PythonOperator(
            task_id=f"training_model_{model_id}",
            python_callable=_training_model,
            op_kwargs={"model": model_id},
        )
        for model_id in ["A", "B", "C"]
    ]

    choosing_best_model = BranchPythonOperator(
        task_id="choosing_best_model", python_callable=_choosing_best_model
    )

    accurate = BashOperator(task_id="accurate", bash_command="echo 'accurate'")

    inaccurate = BashOperator(task_id="inaccurate", bash_command=" echo 'inaccurate'")

    training_model_tasks >> choosing_best_model >> [accurate, inaccurate]

I know that airflow isn't meant to be extremely quick but I was surprised to see this when there is literally no load in the system yet.

Is this normal? If not, could you give me some pointers into what I can look into in order to troubleshoot this?