Jun-te Kim b1ff711260 perf(modelling_e2e): batch SubTask bookkeeping to stop per-property writes ... Even after batching the data writes, the handler still wrote to the DB per property through the orchestrator's SubTask bookkeeping: create + start + complete each self-committed, and _cascade re-listed every sibling and re-saved the parent on every transition — ~5 writes per property plus an O(N^2) cascade. - TaskOrchestrator.run_subtasks: create all children in one INSERT, run each (failures isolated per child), then persist all terminal states in one bulk save and cascade the parent once. Children go WAITING -> terminal; the transient IN_PROGRESS row is never written. - SubTaskRepository.create_many / save_many (bulk INSERT / bulk fetch + update). - _cascade short-circuits when the Task is already FAILED (terminal) — skips the sibling roll-up entirely. - modelling_e2e handler fans out via run_subtasks instead of per-property create_child_subtask + run_subtask. Per N-property batch the SubTask bookkeeping drops from ~5N writes + an O(N^2) cascade to ~2 writes + 1 cascade. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-24 19:26:42 +00:00
..
ara_first_run	refactor(ara): rename FirstRunPipeline → AraFirstRunPipeline (PR #1139 review)	2026-06-01 15:00:33 +00:00
audit_generator	put db engine construction inside handler to avoid import errors in test	2026-06-09 15:18:42 +00:00
landlord_description_overrides	Classify the landlord Hot Water and Heating columns into categories 🟥	2026-06-19 14:07:14 +00:00
magic_plan	define MagicPlanConfig class to get environment variables	2026-06-05 15:46:32 +00:00
modelling_e2e	perf(modelling_e2e): batch SubTask bookkeeping to stop per-property writes	2026-06-24 19:26:42 +00:00
__init__.py	feat(ara): AraFirstRunTriggerBody + ara_first_run lambda skeleton (#1130)	2026-05-30 20:38:15 +00:00