Anonymized production evidence · 2026

KNX to Control4 processing benchmark.

This benchmark summarizes anonymized completed production jobs in CoduWorks through 18 August 2026. It includes 132 completed KNX imports, 248 completed mapping/translation jobs across four AI workflows, nine reprocess analyses, 97 active KNX project files, and 7,393 active generated Control4 devices. It measures server processing time after a job starts; it does not claim a manual-work time saving.

Published: · Dataset cutoff:

01

Observed processing times

WorkflowCompleted runsMedian90th percentileMaximum
KNX import13235.7 s130.7 s522.8 s
Location mapping1139.4 s20.4 s55.1 s
Device mapping generation103182.8 s408.0 s687.6 s
Thermostat processing12146.4 s279.8 s307.9 s
Control4 translation1049.7 s92.4 s98.0 s
KNX reprocess analysis950.0 s149.3 s318.6 s

The median completed KNX import was 35.7 seconds. The median full device-mapping generation job was 182.8 seconds. These are backend durations between recorded start and completion timestamps; queue wait, installer review, export, Composer build, network conditions, and commissioning are outside the measurement.

02

Project and device population

Active KNX projects measured
97 files with a recorded non-zero size
Project file size
Median 13.29 MB · p90 21.04 MB · maximum 80.47 MB
Active generated devices
7,393 total: 6,388 lights, 798 blinds, 109 thermostats, 94 IP gateways, 2 keypad buttons, 1 relay, and 1 motion sensor
Production projects
163 project rows in total; 103 active at cutoff. Deleted projects are excluded from active device and file-size aggregates.

03

Methodology

  1. A read-only PostgreSQL transaction queried production aggregate counts and timestamps on 18 August 2026.
  2. Durations use completed_at - started_at for completed rows with valid timestamps.
  3. Percentiles use PostgreSQL percentile_cont; values are rounded to one decimal second.
  4. File-size statistics include active KNX project rows with a positive recorded size.
  5. Device counts include active C4 device rows grouped only by public device type.
  6. No user, project, file, address, mapping, prompt, or output content was selected or published.

04

Limitations and reproducibility

  • The population is operational, not randomized, and projects may contribute multiple jobs.
  • Hardware load, network conditions, model/provider latency, project complexity, and software version vary.
  • Completed-job duration excludes queue waiting, human review, Composer work, and commissioning.
  • Historic success ratios must not be interpreted as an SLA or a guarantee for a specific project.
  • The aggregate query shape and cutoff are published here; raw project-level rows are withheld to protect customer data.

Use the evidence with the product scope.

Check supported devices, security boundaries, pricing, and the current release before evaluating a project.