Per-task logging costs a third of worker throughput
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 68/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Domaine
- backend, cli, observability, performance
Piste de recherche
Start with threadmill/executor.py, especially configure_logging, the worker command options, and the per-task executor log calls. Trace how TaskExecutor receives logging configuration and how Django's task signal receivers inherit the root level. Done means the worker exposes a configurable level, avoids forcing INFO, and treats per-task executor messages as debug detail while preserving operator control of django.tasks.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Profiling a drain (20,000 echo tasks, one process, one thread, prefetch 128) puts logging at roughly 70 µs of client CPU per task, against a recorded per-task wall of 184 µs. That is about 38% of the worker's throughput, and it is the single largest Python cost in the loop - larger than the Redis round trips it sits next to.
What emits four JSON records per task
threadmill/executor.pylogsExecuting task ...and thenTask ... succeeded(or failed) at INFO for every task.- Django's own
django.tasks.signalsreceivers (log_task_started,log_task_finished) log once more each. They are registered at import and sit at NOTSET, so they inherit the root logger's level. threadmill/executor.py'sconfigure_loggingsets the root logger toINFOunconditionally, so all four records are formatted and written.- The worker's default formatter is
JsonFormatter, which builds a payload dict andjson.dumpses it per record, then writes to stdout and flushes.
Measured inside that 70 µs: 51 µs in StreamHandler.emit and 36 µs in JsonFormatter.format/json.dumps - the formatting, not the log call itself. record_task's lock, by contrast, costs 0.35 µs, and normalize_json 0.5 µs.
Why this is a defect and not just a tuning knob
There is no way to quieten a production worker: configure_logging hardcodes root_logger.setLevel(logging.INFO), and the command exposes --log-format but no --log-level. A deployment that wants WARNING output cannot get it, and it pays a JSON encode and a stdout flush per task for the privilege.
Suggested fix
- Add a level option to the worker command (and to
TaskExecutor), defaulting to something quiet. - Demote the two per-task executor records to
DEBUG; "task started/succeeded" is trace-level detail, and the task itself is the interesting signal. - Leave the level of
django.tasksto the operator rather than forcing the root logger to INFO.
Benchmark fairness
The comparison harness runs celery and dramatiq with --loglevel=WARNING, while threadmill currently cannot run below INFO, so part of the chart gap is threadmill logging its own benchmark. Fixing this makes the comparison apples-to-apples as well as making production faster.
Discovered while validating per-task performance claims; the profiling numbers are from a loaded machine, so treat the shares as the durable result and the absolute microseconds as this box's.
- Langage dominant
- Python
- Étoiles
- 21
- Forks
- 2
- Merge moyen
- 12 h 39 min
- PR mergées (30 j)
- 27
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
-
[Bug]: Queen's own Ollama model loses num_ctx when a running session switches to itPeut-être pris @anasamin26 l’a pris aujourd’hui. Ouvertebug enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
aden-hive/hive#7508 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
llm translation
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
BerriAI/litellm#47884 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
bug 🐛
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
netalertx/NetAlertX#1856 · 1 réaction ·
Les mainteneurs répondent en général sous 1 jour