Release planning

CadCraft 0.11 impact map

Every fix and feature lined up for 0.11, and what each one touches: which apps, and which layers of the stack.

ProjectCadCraft
Sheet0.11 impact
Items799
Date2026-11-22
181Fix
383Feature
8Spike
35Platform
3Site ops
153Sanity check
36Decision
0Note
≈ 96days in the written 0.11 plans
  • Planned 45 on the plan for the release it is filed under
  • Built 449 built and working in /lab (the dev builds). Whether the public has it is its reach: "in the lab", "Live" (the last gate) or "switched off"; see docs/REACH-LIVE.md
  • Partly built 32 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 3 the live site already says it is coming
  • Moved 2 moved here from an earlier release or wishlist
  • Found 2 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 49 recommended in a spike or session log; owner to choose
  • Community please test 143 built and in /use; a Discord post gives the steps and the expected result and asks people to try it on their own devices, files or know-how
  • Decision Time 74 a decision, check, file, key, flag or go only you can give; folds into the list once answered

Built means built and working in the lab. Live means the public can use it, and is the last gate: 3 Built · Live, 446 Built · in the lab.

Sheet 1 · impact areas

Where 0.11 lands

How many items touch each app and each layer, by kind. One item can touch several areas, so the rows add up to more than the item count. Pick a row to filter the schedule below.

Impact areaFixFeatureSpikePlatformSite opsSanity checkDecisionNoteAll
Apps
CadCraft 89 154 4 10 1 51 11 – 320
BimCraft 79 178 5 10 2 70 18 – 362
ModelCraft 60 81 2 10 1 41 4 – 199
MarkupCraft 46 59 2 9 1 18 1 – 136
TakeoffCraft 50 59 2 9 1 21 3 – 145
CivilCraft 69 131 3 11 1 35 3 – 253
DetailCraft 58 61 2 9 1 26 2 – 159
PartCraft 57 78 2 9 1 37 3 – 187
Studio 12 43 3 9 1 30 5 – 103
SuperCad Studio 9 109 2 7 – 23 5 – 155
Layers
Site and services 15 25 – 10 2 2 8 – 62
Desktop host 7 22 2 10 – 7 2 – 50
App shell 25 32 – 7 – 4 2 – 70
App code 69 193 4 6 1 9 16 – 298
Our engines 8 71 3 1 – 4 10 – 97
Vendor engines – 2 – – – – 1 – 3
Drawing surface 1 – – – – 1 – – 2
Help and words 2 9 1 – – 2 – – 14
Tests and tooling 4 9 1 3 – 4 2 – 23

Sheet 2 · schedule

Every fix and feature

Grouped by track. App chips carry each app’s layer colour; Studio is in ink. "Waits on" names what has to happen first; the small lines under it say who asked and where the item is written up.

Add an item Fork map (Rust and C++ forks) The roadmap

Issues sync every 10 minutes; last sync Nov 22, 2026 10:40 am.

ItemWhatAppsLayersStatusDaysWaits onIssues
Performance roadmap — wave 3 49
FixPERF.42 Link to PERF.42Comment on PERF.42 Website: Library browse sorts every published item on a computed key and counts them again on every page; at 100x it is seconds per page

Partly built (site-inbox-11 2026-11-20). Migration 157-library-sort-at.sql APPLIED on the live DB 2026-11-20 (bin/install.php, with 158 and the sandbox copy: 12 s in all; 13,875 rows, table 11 MB): library_items.sort_at DATETIME NULL (nullable on purpose: until library-11's writers keep it, a NULL row is still read through the old expression), filled from COALESCE(current version published_at, updated_at) with updated_at = updated_at so no item's updated_at moved (0 NULL, 0 differing from the formula), and idx_browse_sort (visibility, status, sort_at, id), idx_browse_kind (visibility, status, kind, sort_at), idx_browse_cat (visibility, status, category, sort_at). Measured, mysql client incl. about 15 ms start-up, 3 runs: default browse order (24 ids) 64-75 ms with the COALESCE + join -> 17 ms with ORDER BY sort_at DESC, id DESC. Nothing reads the column yet. Was: Partly built (perf-site-10 2026-11-13). COUNT, category chips and class counts leave out the join to library_versions when no condition reads it (primary-key join, same rows, index-only on idx_browse). Not built: the sort_at column and keys for the default sort (64 ms filesort), keyset pages, cached counts: every writer of current_version_id and the importers must change together, designed in docs/LIBRARY-1000X-DESIGN.md 3.1-3.3. Was: LibraryItems.php:152-157 orders by COALESCE(v.published_at, i.updated_at) DESC after the join, so LIMIT cannot help: EXPLAIN shows all 13,846 rows read through idx_browse, joined, then a filesort (64 ms) plus SELECT COUNT(*) (30 ms) plus categoryCounts (:171, 30 ms) per request; OFFSET 960 BUILT 2026-11-21 (perf-finish-11), lane site, in /lab (a Discord member) only: All 17 library_items writers keep sort_at (LibraryItems::syncSortAt, updated_at untouched); drift check bin/library-sort-at.php (one drift fixed). With LIBRARY_SORT_AT=1 a browse page 118 -> 15 ms (page 400: 155 -> 36 ms), pages, order and totals identical in 193 cases; test-library-pages 406 / 0 with the switch on and off. LIVE 2026-11-22 (owner's go: "go do what is necessary"): .env LIBRARY_SORT_AT=1 is on; nightly drift check /etc/cron.d/cadcraft-library-sort-at (04:40, www-data, logs/library-sort-at.log); check at switch-on: 0 of 13,886 rows differ; test-library-pages 408 / 0 with the switch on.

– Site and services Built · in the lab 3 – docs/0.9-sessions/perf-wave3/
FixPERF.43 Link to PERF.43Comment on PERF.43 Website: Library search is LIKE '%q%' on four columns while an unused FULLTEXT index sits on exactly those columns

Partly built (site-inbox-11 2026-11-20). Migration 158-library-search-ngram.sql APPLIED on the live DB 2026-11-20: FULLTEXT ft_search_ngram (name, maker, model, description) WITH PARSER ngram beside ft_search (kept). The server's ngram_token_size is 2 (a startup variable shared by every site on this MySQL, not 3). Measured, MATCH ... AGAINST ('door') count: 52 ms (LIKE substring) -> 16-18 ms. Caution for the switch: two FULLTEXT indexes now cover the same four columns, so a MATCH over them may use either; library-11 should confirm which one browseWhere gets (and that LIBRARY_SEARCH_FULLTEXT results are unchanged) before it flips. Nothing reads the new index yet. Was: Built behind .env LIBRARY_SEARCH_FULLTEXT=1, OFF (perf-site-10 2026-11-13). It is not the same result set: on 28 words FULLTEXT word starts found 0 items the substring search misses and missed 0 to 397 per word that the substring search finds (table 942 against 545, bed 495 against 273, light 1,029 against 835; matches inside longer words). Waits on the owner: is search by word start the product? Same pages, HTML identical while off. Was: LibraryItems.php:200 browseWhere runs (i.name LIKE ? OR i.maker LIKE ? OR i.model LIKE ? OR i.description LIKE ?) with %q%; the schema has ft_search (name, maker, model, description) and sys.schema_unused_indexes lists it. EXPLAIN: 52 ms scanning 13,846 rows today versus 16 ms with MATCH … AGAINST ('door' IN BOOLEAN MODE) reading 1,324 rows from the index; at 1 M items about 3.7 s versus tens of ms. Fix: for queries of three or more characters use MATCH(i.name, i BUILT 2026-11-21 (perf-finish-11), lane site, in /lab (a Discord member) only: Library search pre-filters with MATCH AGAINST on the ngram index (migration 158) behind LIBRARY_SEARCH_NGRAM, the existing substring test still decides: identical results over the whole table on 327 queries (bin/test-library-search-ngram.php 442 / 0); rare words much faster (zeman 38 -> 0.9 ms), common letter pairs slower (hinge 31 -> 55 ms). LIVE 2026-11-22 (owner's go): .env LIBRARY_SEARCH_NGRAM=1 is on (ngram pre-filter, the same results as before; word-start LIBRARY_SEARCH_FULLTEXT left off); test-library-search-ngram 442 / 0, test-library-pages 408 / 0 with it on.

– Site and services Built · in the lab 1 – docs/0.9-sessions/perf-wave3/
PlatformPERF.44 Link to PERF.44Comment on PERF.44 Website: session_activity and analytics_visitors hold 1.6 M rows and 1,015 MB (83 % of the database), 42 % bots, no retention, one table never read

Partly built (site-11 2026-11-20). bin/test-analytics-prune.php 8/0. New switch ANALYTICS_VISITORS_OFF=1 (OFF) stops the analytics_visitors upsert on every page view (the table is read by nothing: checked across public_html, bin, tools); the retention job keeps pruning what is there. The nightly prune is still off (ANALYTICS_PRUNE=1, 400 days). Was: Partly built (perf-site-10 2026-11-13). AnalyticsRetention + bin/analytics-prune.php (batches of 5,000 on the date index, one run at a time, tests 8/0), OFF until .env ANALYTICS_PRUNE=1; 400 days default (ANALYTICS_RETENTION_DAYS), optional shorter bot window; today it counts 0 rows (oldest row 2026-10-10). Cron line is in the script header for the owner. Not built: no rows for bot page views, the daily rollup table, stop writing analytics_visitors, dropping idx_session. Was: Measured: session_activity 1.02 M rows / 646 MB growing 51,086 rows a day (21,675 of them is_bot = 1), analytics_visitors 597k rows / 369 MB growing 38,644 a day because a cookie-less client gets a fresh visitor id on every request; the table is written on every page view (Analytics.php:75) and read nowhere. Nothing prunes either (no DELETE in bin/ or the classes except the smoke test's own rows). The report queries full-scan the table (EXPLAIN ANALYZE: summary 1.8 s, topPages 2.4 s, each audience group 1.7 s, tryOpens 1.3 s), so the nightly warm job is roughly 60 to 80 s of scans that push the whole table through a 1 GB server-wide buffer pool these two tables alone fill. CadCraft analytics is about 1.1 inserts a second, over half of all INSERTs on this MySQL, each an fsync (two autocommits per page view). At 10x the warm job takes ten minutes and evicts every other database on the server. Fix: (1) do not store bot page views as rows (count per day per bot name in a small table) and give a visitor with no cc_vid cookie no analytics_visitors row until the second request; (2) retention for humans (owner's number; 30 days for any bot rows kept…

– Site and services Built · in the lab 4 Owner: ANALYTICS_PRUNE=1 with the cron line in bin/analytics-prune.php (400 days), and ANALYTICS_VISITORS_OFF=1 docs/0.9-sessions/perf-wave3/
FixPERF.46 Link to PERF.46Comment on PERF.46 Website: staff pages with uncached GROUP BY scans: /admin/library/metrics 887 ms, /admin/library 422 ms, /admin/hardware 265 ms

Partly built (site-11 2026-11-20). Nothing new in code; measured with STAFF_REPORT_CACHE=1 in a child process (rule 75): /admin/hardware 993 ms to 35 ms (second view), /admin/library/metrics 7,226 ms to 158 ms, /admin/library 1,011 ms to 36 ms; the first view after ten minutes still pays the full cost. /admin/hardware HTML identical both ways. The hardware summary's 13 GROUP BYs stay as they are (ties in ORDER BY n DESC LIMIT 30 are undefined, so one pass could not be proved identical). The Library report classes are library-11's. Was: Partly built (perf-site-10 2026-11-13). RoadmapItems::groups (7 calls) and MailLog::countsByStatus (2) once per request: /roadmap-issues 117.7 ms and 20 queries to 73.5 ms and 13. LibraryMetrics::report, possibleDuplicates and HardwareReports::summary read a 10-minute cache behind .env STAFF_REPORT_CACHE=1, OFF (a figure may be 10 minutes old). The hardware summary's 13 GROUP BYs were not merged: ties in ORDER BY n DESC LIMIT 30 are undefined, so identical output could not be proved. Was: LibraryMetrics::report (LibraryMetrics.php:129, :151, :156) is 430 ms of the metrics page, one statement 222 ms (a 41k-row range on uq_once_a_day, a sort and COUNT(DISTINCT who)), linear in rows (2,157 new rows a day, 4 s at 10x). LibraryVersions::possibleDuplicates (LibraryVersions.php:587-604) is 383 ms per /admin/library view, a self-join over 27k versions that finds nothing today. HardwareReports::summary (HardwareReports.php:93) runs 13 GROUP BY scans of all 25,914 rows (240 ms; idx_day cannot help because every row is inside 90 days). MailLog::countsByStatus (MailLog.php:180) runs twice on /admin/mail (53 ms); RoadmapItems::groups runs seven times on /roadmap-issues with the same arguments. Fix: Cache::remember(…, 600) around report, summary and possibleDuplicates (the dashboard already works this way); better for duplicates, set duplicate_of_version_id at publish time in LibraryVersions::create (one indexed lookup on idx_item_sha / idx…

– Site and services Built · in the lab 1 Owner flips STAFF_REPORT_CACHE (staff figures up to 10 minutes old); first view after expiry is still slow docs/0.9-sessions/perf-wave3/
FixPERF.47 Link to PERF.47Comment on PERF.47 Website: missing, redundant and dead indexes (DDL in the report)

Partly built (site-11 2026-11-20), migration 156: dropped session_activity.idx_session and analytics_visitors.idx_user and idx_bot, which nothing reads (grep of public_html, bin and tools: the only session_id match is a test's INSERT; analytics_visitors is written and never read). Applied by bin/install.php (only 156 was pending), metadata-only on InnoDB, no table or row touched. Pages unaffected (no output reads these). Left: discord_messages author and time indexes wait for the Discord reader (1,852 rows, nothing to measure). Was: Partly built (perf-site-10 2026-11-13), migration 153. idx_submission on library_versions (46 ms scan to 0.42 ms), idx_action_time on audit_log (17.3 to 0.56 ms), idx_item_key on roadmap_items (0.63 to 0.40 ms); dropped library_metrics.idx_day and broadcasts.idx_status (prefixes). Not done: session_activity.idx_session and the analytics_visitors indexes wait for PERF.44's retention; discord_messages waits for the reader. Was: Missing: library_versions.submission_id (LibrarySubmissions::outcome, LibrarySubmissions.php:353, full-scans 27,185 rows, 40 ms per call; 26,537 versions carry a submission id) → ADD KEY idx_submission (submission_id). audit_log.action (Audit::search/searchCount :157-184 with a.action LIKE ?, StripeApprovals::siteRecords :71, DiscordConversations::itemsForMatching :321, Broadcasts::version :463; 52,791 rows growing 1,820 a day) → ADD KEY idx_action_time (action, created_at). roadmap_items.item_key alone (RoadmapSuggestions::findItem :28, ReplyDrafts::usedItems :99 query without release, so uq_release_key cannot serve them; every /suggest review runs it) → ADD KEY idx_item_key (item_key). discord_messages author_id and posted_at (DiscordInbox.php:431, :569, :54, :58; low, read BUILT 2026-11-21 (perf-finish-11), lane site, in /lab (a Discord member) only: Migration 160 (discord_messages idx_author, idx_posted) applied; author lookup 0.445 -> 0.159 ms, identical answers. With migrations 157/158 every index in the report is done.

– Site and services Built · in the lab 1 – docs/0.9-sessions/perf-wave3/
FixPERF.48 Link to PERF.48Comment on PERF.48 Website: ordinary Library page views read every published item (publicStats, LanguageNames::inUse, makers, forUser without LIMIT, a 652 KB cache per page)

Partly built (perf-site-10 2026-11-13). LibraryMetrics::totals decoded once per request (650 KB JSON per card before). publicStats measured: aggregate SQL is slower than the PHP loop (66 ms against 43), so it was left; inUse, makers and forUser untouched. A stored stats row is the design (docs/LIBRARY-1000X-DESIGN.md 3.6). Was: LibraryItems::publicStats (LibraryItems.php:278-295) pulls every published row with its author and version into PHP to count authors and categories: 42 ms per view of /library and /library/author. LanguageNames::inUse (LanguageNames.php:77-83) joins all items to their versions (a UNION with addon_listings) on every Library page to learn that two languages exist: 28 to 44 ms. LibraryItems::makers (:268) SELECT DISTINCT maker over all published rows per browse page (fast today, linear later). LibraryItems::forUser (:221) has no LIMIT: the system account's /library/mine loads 13,844 rows. LibraryMetrics::totals is cached, but the cache file is 652 KB of JSON decoded on every card page (that is the 367 ms "PHP" of /library/browse). Fix: publicStats as one GROUP BY or Cache::remember 600 s with the key dropped in LibraryItems::refresh; cache inUse and makers the same way (or compute inUse in the seed); forUser paged by 50 like LibrarySubmissions::forUser; metrics labels read the per-ref rows (idx_ref) for the 48 refs on the page instead of the whole totals file. At 1 M items each of these is seconds; with the fix they are constant. library-11 2026-11-20: publicStats and makers cached behind LIBRARY_STATS_CACHE=1 (see PERF.12, identical output). Not done: LanguageNames::inUse (28 to 44 ms) is site-11's class; forUser has callers that expect every row (a LIMIT changes output): Inbox to site-11. LANDED 2026-11-20 (inbox-11b) LanguageNames::inUse() reads through Cache::remember (600 s) when LIBRARY_STATS_CACHE=1; off = unchanged. Cold, warm and uncached output identical. (inbox-11b)

– Site and services Built · in the lab 1 Owner flips LIBRARY_STATS_CACHE. docs/0.9-sessions/perf-wave3/
FixPERF.49 Link to PERF.49Comment on PERF.49 Website: every signed-in page view runs the account-menu queries (5 to 6 statements; 12 Licenses::forOrg calls on /account)

Partly built (site-11 2026-11-20). Behind .env ACCOUNT_PAGE_MEMO=1, OFF: /account answers Organizations::forUser, Licenses::forOrg, Licenses::seatFor and StoragePlans::inForce once per request (PageMemo; the page only reads). Measured in a child process with the switch on, HTML byte-identical: 66 queries to 39, SQL 18.9 ms to 8.2 ms, 65 ms to 50 ms (load 30+). Every other signed-in page already runs each of them once (1.5 ms), so nothing else changes; the 60 s session cache the row proposed is still not built (four services would have to invalidate it). Was: Checked (perf-site-10 2026-11-13), not built: measured 1.5 ms per signed-in page. A memo needs begin() on every signed-in page, or a session cache invalidated by four services (Licenses, Organizations, StoragePlans, seats): risk higher than the gain today. Was: navbar.inc:36 → Organizations::listedFor → forUser (Organizations.php:181, a correlated member COUNT), then per workspace Licenses::summary → forOrg (two statements), Licenses::seatFor and StoragePlans::inForce: 5 to 6 statements and about 1.5 ms on each of the 61 pages profiled, 12 forOrg calls on /account. With one workspace per account this is small; with teams it is three statements per workspace per page. Fix: compute listedFor once per request (static memo) and keep the menu's result in $_SESSION with a 60 s stamp, invalidated by Licenses::assign/unassign/grant and Organizations::addMember/removeMember (or the touched() hook the dashboard already uses).

– Site and services Built · in the lab 1 Owner flips ACCOUNT_PAGE_MEMO (gain 66 to 39 queries on /account; risk none seen, output identical; roll back: unset it) docs/0.9-sessions/perf-wave3/
PlatformPERF.53 Link to PERF.53Comment on PERF.53 Apps: 29.6 MB of byte-identical files under different URLs across the eight releases, and every new release re-downloads 98 % unchanged files

Planned (code-mains2-10 2026-11-16): not started. Baseline measured and saved (docs/results/0.10/code-mains2-10-shared-before.txt): 822 distinct contents under 2,548 URLs, 33.2 MB of extra copies. Fixing it changes released-build packaging and the 0.9 folders (rule 60: the owner's), so it needs the owner's word on the approach first. Was: tools/perf/addons-shared.mjs hashed every file of the eight current releases: 665 distinct contents under 2,163 URLs, 29.6 MB extra on the wire for a person who opens more than one app (cabinetcraft add-on in four apps 5.8 MB, dwg/ 3.0 MB, ifc schemas in four apps 2.3 MB, regs in four 2.3 MB, m3d 1.3 MB, crs-db.json 914 KB three times, host.js / addons.js / libitem.js eight times). Across releases: CadCraft 0.8.1 → 0.8.2 kept 2,084 of 2,127 files byte-identical (158 MB) and every one is re-downloaded under the new version URL; the same for every app and every "Save for offline" re-save (PERF.15). Vendor libraries are fine (one URL each, pinCurrent works). Change: a shared /assets/lib/<name>/<content-hash>/ URL for lib/* copies and shared add-ons (release-app.php pins it like vendor paths; the import map aliases ./dwg/x.js to it), or content-hashed file names so an unchanged file keeps its URL across releases. Both shrink the import map, which lists every file because ?v= busting needs an entry per module (499 entries / 48 KB in CadCraft, 772 / 78 KB in BimCraft per page view; AppBuilds.php:391-397).

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Site and servicesApp shell Planned 8 – docs/0.9-sessions/perf-wave3/
PlatformPERF.58 Link to PERF.58Comment on PERF.58 Apps: an installed add-on package is relinked from blob modules on every start (hvac 334 ms, plant 756 ms) and ships as base64 JSON

addons.js linkPackage turns each verified package into blob: module URLs every start: hvac 0.9.0 (193 files, 1.8 MB; 2.4 MB as base64 JSON) costs 334 ms per start (link 115, import 55, verify 6); plant 756 ms (import 447). The Ed25519 plus sha256 check is cheap (6 to 11 ms for 100 to 193 files); blob modules get no HTTP cache and no V8 code cache, so the cost repeats on every visit and grows with file count. Change: keep the signature check but serve verified packages from the service worker under a stable /addons/pkg/<sha>/<path> scope (or cache the linked texts and import() a persistent URL) so modules get code caching; stop base64 in the package JSON (binary zip, about 34 % smaller). AddonPackages.php, addons.js, sw.js.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft App shellSite and services Planned 3 – docs/0.9-sessions/perf-wave3/
PlatformPERF.62 Link to PERF.62Comment on PERF.62 Server: the opcache interned-strings buffer is full and the cache restarts during the day

Measured: opcache interned strings 8.0 of 8.0 MB used (70,128 strings), oom_restarts 1 at 20:11 UTC today on a cache started 01:58; 1,195 scripts, 54 of 128 MB. After each restart every PHP file of every vhost recompiles (CadCraft alone 379 scripts / 33 MB): a CPU spike and slow first requests several times a day. Change in /etc/php/8.3/apache2/conf.d/10-opcache.ini: opcache.interned_strings_buffer=32, opcache.memory_consumption=256, then apache2ctl graceful. Healthy otherwise: hit rate 99.94 %, realpath cache 14 % used, autoloader one is_file per class, .env parse 0.04 ms, bootstrap 2 to 3 ms, DB connect 0.8 ms.

– Site and services Decision Time 1 Owner: server-wide PHP setting (shared by about 80 vhosts), no functional risk. docs/0.9-sessions/perf-wave3/
FixPERF.63 Link to PERF.63Comment on PERF.63 Website: a distributed crawl of /roadmap-issues filter combinations is about half of all PHP page requests (485,944 in 8 days, 172 ms and 1.4 MB of HTML each)

Partly built (site-11 2026-11-20). Row cache behind .env ROADMAP_ROWS_CACHE=1, OFF: the visitor view's schedule rows are rendered once per release (one 1.4 MB Cache entry per release, replaced when items, links, comments or hidden names change, or after 10 minutes) and a filtered view only adds `hidden`. bin/test-roadmap-rows-cache.php: 7 filters, off, on cold, on warm, HTML byte-identical in all 21 renders; a filtered render 500 to 640 ms down to 83 to 115 ms (load 30+; the render of a cached release is a string copy per row). Earlier: nofollow on the filter links, and robots Disallow behind ROBOTS_DISALLOW_ROADMAP_FILTERS (off). Was: Partly built (perf-site-10 2026-11-13). rel=nofollow on the map's filter links (HTML otherwise identical); robots.txt Disallow: /roadmap-issues? behind .env ROBOTS_DISALLOW_ROADMAP_FILTERS=1, OFF (the page stays reachable and noindex). The render cache is not built: the crawl's URLs are nearly all different, so a per-URL cache would rarely hit and would fill the disk with 1.4 MB files; the fix is to render the item list once per release and apply the filter as markers. Was: Access logs: 485,944 requests to /roadmap-issues in 8 days (184,651 on Nov 6); in the last 5 hours 24,548 requests from 17,356 distinct IPs with browser user agents and fake referers, every permutation of ?app=&channel=&kind=&layer=&release=; 23,831 of the last 49,776 dynamic requests. Each costs 172 ms of PHP, 23 queries and 1,416 KB of HTML (112 KB gzipped): about 23 CPU-hours and 54 GB of egress in 8 days, invisible on /admin/analytics because Analytics::SKIP_PREFIXES has /roadmap-issues. The crawl ignores robots, so per-IP throttling cannot help. Change: render the item list once per release into Cache (60 s) and filter from it (172 to about 20 ms); rel="nofollow" on every filter link and a canonical URL per release; if the page stays reachable by link, filter client-side on the cached list. Removes about 45 % of PHP CPU and most HTML egress today; the …

– Site and services Built · in the lab 3 Owner flips ROADMAP_ROWS_CACHE and ROBOTS_DISALLOW_ROADMAP_FILTERS (visitors see item changes within a minute of the fingerprint change) docs/0.9-sessions/perf-wave3/
FixPERF.64 Link to PERF.64Comment on PERF.64 Website: a session file is written for every anonymous page view (312,607 files, 1.3 GB, 92,632 a day, GC 38 s)

Partly built (site-11 2026-11-20). Behind .env SESSION_LAZY=1, OFF: a first visit (GET, no session cookie, HTML page, not /api /download /assets) opens no session file; is an array for the request, the output is held (4 MB), and cc_lazy_session_commit() opens the session at the end only if the page wrote into it (the cookie goes out before the held output). A write that cannot be kept is logged, never silent. bin/test-lazy-session.php 37/0 on the real site under PHP's built-in server: 20 public pages byte-identical off and on; /great-eight /faq /pricing /library /use /use/cadcraft /legal/terms /press-kit /tutorials /status /whats-new leave no file and no cookie; /login /signup /suggest /roadmap /roadmap-issues /download /education /forgot-password still get theirs (they carry a CSRF form); CSRF refusal (no cookie, wrong token), wrong-password round trip with the email kept, sign-in, flash once, /account, /use/cadcraft keep working. Not solved: the crawled page /roadmap-issues has a form, so it still opens a session (the 48 h sweep keeps handling those). Was: Checked (perf-site-10 2026-11-13), not built: bootstrap.php starts the session before any page code and more than a hundred places write $_SESSION directly, so a lazy start would lose writes on a first GET (CSRF tokens, flash, sign-in). Needs a single session write path first; then the switch. Was: sessions/ holds 312,607 files, 98.8 % under 120 bytes (a CSRF token or nothing), 92,632 written in 24 h and still 7,574 an hour after today's crawler change; the directory inode is 142 MB (a directory never shrinks); session-gc takes 38 s every 6 h (38,589 CSRF-only files removed per run). Every page view is open, flock and write of a file; the per-session lock also serializes one visitor's parallel requests. (FX.136 shortened the lifetime; this removes the cause.) Change: start the session lazily, only when a cc_session cookie arrives or something is written (csrf_token(), flash(), sign-in); a signed double-…

– Site and services Built · in the lab 3 Owner flips SESSION_LAZY (fewer session files for pages without a form; /roadmap-issues still opens one); a form-free suggest box on that page would remove the docs/0.9-sessions/perf-wave3/
FixPERF.65 Link to PERF.65Comment on PERF.65 Website: Vary: Referer on every response, assets included, so the browser caches each shared module per referring page and no shared cache can hold them

Checked again (site-11 2026-11-20): still the owner's rule. Vary: Referer confirmed on /assets/js/app-state.js. Nothing changed. To drop it: keep the a Discord member-build path rule and send no-store from PHP for lab pages (header.inc when is_a Discord member); shared assets opened from /lab would then be cached for a week. The owner chooses. Was: Checked (perf-site-10 2026-11-13), owner decision: the Referer test in public_html/.htaccess is the owner's 2026-10-26 lab rule (every file a /lab page asks for, shared ones included, is fetched fresh). Dropping it would cache shared files for a week when opened from /lab. Alternative: no-store by path for a Discord member builds and from PHP for lab pages, shared files cached. Was: public_html/.htaccess:28 wraps the lab no-store rule in <If "%{REQUEST_URI} =~ … || %{HTTP_REFERER} =~ …">, and Apache adds Vary: Referer,Accept-Encoding to every response that passes it, cadcraft.js included. A browser's cache entry for a shared file is then keyed by the referring page: the same assets/js/*.js fetched under /use/bimcraft after /use/cadcraft, or /library, misses; a CDN or shared cache cannot store the assets. With 400 requests per app start this counts. Change: keep <If "%{REQUEST_URI} =~ m#^/assets/apps/[^/]+/a Discord member/#"> for a Discord member builds and send Cache-Control: no-store for lab pages from PHP (header.inc when is_a Discord member) instead of the Referer match.

– Site and services Planned 1 Owner decision: drop the Referer test in public_html/.htaccess (shared files then cached a week when opened from /lab) docs/0.9-sessions/perf-wave3/
PlatformPERF.66 Link to PERF.66Comment on PERF.66 Server: Apache and TLS settings for a 400-request app start: MaxKeepAliveRequests 100, no OCSP stapling, RSA-2048, no HSTS, MaxConnectionsPerChild 0

Measured: a TLS handshake is 25 to 30 ms on localhost (RSA-2048, session tickets off by certbot, no stapling: "OCSP response: no response sent"); with MaxKeepAliveRequests 100 and six connections a 400-request CadCraft start forces at least four extra handshakes (each about two round trips plus CPU for a visitor). Prefork MaxRequestWorkers 150; 36 to 40 children at 50 MB (81 MB max) = 2 GB; MaxConnectionsPerChild 0 so a mod_php child never recycles. HSTS is on api.getcadcraft.com and the forks, not on getcadcraft.com. Changes: MaxKeepAliveRequests 1000 (or 0) in /etc/apache2/apache2.conf; SSLUseStapling On plus SSLStaplingCache shmcb:${APACHE_RUN_DIR}/stapling(128000) in mods-available/ssl.conf; certbot --key-type ecdsa for getcadcraft.com and api (halves handshake signing); Header always set Strict-Transport-Security "max-age=31536000" on getcadcraft.com; MaxConnectionsPerChild 10000 in mpm_prefork.conf. All moot or smaller after PERF.1 (HTTP/2), which these numbers also strengthen.

– Site and services Decision Time 1 Owner: apache2.conf, mods-available/ssl.conf and mpm_prefork.conf are server-wide (about 80 vhosts); the ECDSA certificate and HSTS header are this site's. docs/0.9-sessions/perf-wave3/
PlatformPERF.67 Link to PERF.67Comment on PERF.67 Server: MySQL settings versus the data on the box: a full 1 GB buffer pool for 5.2 GB of data, table cache overflowing, slow log off

Measured: innodb_buffer_pool_size 1 GB with 1,024 free pages and wait_free 74,540 against 5.2 GB of data plus index across 56 schemas (cadcraft_db 1.23 GB; the two analytics tables alone are 1 GB); table_open_cache 4000 full with 110,482 overflows; Sort_merge_passes 1.1 M with a 256 KB sort buffer; innodb_io_capacity 200 on an SSD; slow_query_log OFF and long_query_time 10 (7 hits in 12 days; nothing below it is known). Also from the SQL track: 64,469 COMMITs at 2.76 ms (innodb_flush_log_at_trx_commit = 1, every autocommit an fsync) and SET time_zone run 1.28 M times = one per connection (no persistent connections). Changes: innodb_buffer_pool_size 4G (SET GLOBAL plus mysqld.cnf), table_open_cache 8000, sort_buffer_size 1M, innodb_io_capacity 1000 / max 4000, slow_query_log ON with long_query_time 0.5 and log_queries_not_using_indexes capped, init_connect = "SET time_zone='+00:00'" if persistent connections are wanted; flush_log_at_trx_commit 2 is a server-wide trade (a second of rows lost on a crash) the other sites would share: the analytics row removes most of the fsyncs anyway. Healthy: pool hit rate 99.9 %, 2 disk temp tables of 3.6 M, redo 430 MB a day, max_used_connections 44 of 151.

– Site and services Decision Time 1 Owner: shared MySQL (56 schemas); all settings are dynamic, no restart; the pool adds about 3 GB to mysqld's 2.8 GB RSS (15 GB free). docs/0.9-sessions/perf-wave3/
PlatformPERF.68 Link to PERF.68Comment on PERF.68 Server: disk at 75 % with 90 GB reclaimable (a 56 GB Rust build tree, tmp/ build trees, both 0.8 downloads, a lang-overlay cache); logs rotated monthly

Measured: / is 290 of 388 GB. desktop-shell src-tauri target 56 GB (the forks' target moved to W: on 2026-11-08; this one did not; memory rule: never rebuild forks on the VPS), stores/build 18 GB, tmp build trees about 13 GB (editions, public-repos, studio-suite-0.9-a Discord member, devshell, live-apps-www*), downloads 0.8 and 0.8.1 both on disk (2.1 GB each; 0.7 and older moved to the CDN), three byte-identical frozen copies per app (hardlinking would save about 1.3 GB), tmp/cache/lang-overlay 981 MB with no TTL; access.log 345 MB a day uncompressed for a month (2.76 GB now). Noise: mec-broker logs two lines a minute when idle, a Discord member-sandbox-sync logs the same schema drift (team_join_codes.used_at) every 10 minutes, mail-poll logs a PHP array_merge(stdClass) error every 5 minutes (a ContactMail bug). Changes: move or delete the Rust target, clean tmp/ after each release, TTL on lang-overlay, hardlink identical files across frozen versions in bin/release-app.php, publish 0.8 downloads to the CDN like 0.7, weekly (or daily access) logrotate, quiet the idle broker line, fix the sandbox drift and the mail-poll error. About 90 GB back (75 % to about 52 %). closing 2026-11-16: Planned → Owner. Server-wide logrotate and disk settings (KICKOFF § Not a session); no session work.

– Site and servicesTests and tooling Decision Time 1 Owner: /etc/logrotate.d is server-wide; tmp/downloads-replaced (4.7 GB) is the "never deleted" policy and stays. docs/0.9-sessions/perf-wave3/
FixPERF.69 Link to PERF.69Comment on PERF.69 Website: the developer API makes three writes per keyed call (last_used_at, throttle, request log), health polls included

Partly built (site-11 2026-11-20). bin/test-a Discord member-api.php 149/0 with DEVAPI_LIGHT_WRITES=1 given to the process and with it off. By the code a repeat keyed call writes one row (the throttle INSERT) instead of three, and a 200 on /v1/health no row in a Discord member_api_requests. Not measured under load: the measuring script needed a licensed fixture account the session did not make. Was: Built behind .env DEVAPI_LIGHT_WRITES=1, OFF (perf-site-10 2026-11-13): last_used_at at most once a minute per key (and when the caller's address changes), no a Discord member_api_requests row for a 200 on /v1/health; every other call and every failure is still logged. test-a Discord member-api 149/0 with the switch off; not measured under load. Was: DevKeys::inspect runs UPDATE a Discord member_api_keys SET last_used_at, Throttle::hit an INSERT and DevApi::log an INSERT on every call, 200s on /v1/health and 404s too; each autocommit is an fsync with innodb_flush_log_at_trx_commit 1. Load test: api host /v1/health 679 req/s, /v1/endpoints 763, /v1/status 364 at c=10, zero failures (the floors are fine: health 3.6 ms). At 1000x (an integrator polling once a second) the writes are the cost. Change: update last_used_at at most once a minute per key, skip the request log for health 200s, keep it for everything else; a Discord member_api_requests is pruned at 30 days already.

– Site and services Built · in the lab 1 Owner flips DEVAPI_LIGHT_WRITES (gain: 3 writes to 1 per call; risk: last_used_at up to a minute old, no log row for health 200s) docs/0.9-sessions/perf-wave3/
Sanity checkPERF.70 Link to PERF.70Comment on PERF.70 Server: operations checks: two cron jobs without a lock, status-check's serial probes, no Apache scoreboard, static files gzipped per request

Partly built (site-11 2026-11-20). flock added to bin/upgrade-notify.php tick (cron every minute; two overlapping runs could mail twice; tested: a second run exits in 0.1 s while the lock is held). Audited every bin script a cron file runs: the others have a lock, flock in the cron line (cdn-resize, cdn-short) or run once a day. status-check keeps its 60 s cap. Owner's: the /server-status vhost rule and any cron file. Was: Partly built (perf-site-10 2026-11-13). flock added to bin/mail-poll.php and bin/a Discord member-sandbox-sync.php (tested: a second run exits at once); StatusMonitor::runChecks stops retrying failed probes after 60 s (test-status 36/0). Owner's: the /server-status vhost rule and any cron file. Was: bin/mail-poll.php (IMAP, every 5 min) and bin/a Discord member-sandbox-sync.php (every 10 min) have no flock while every other job has one; status-check runs 7 probes serially with 12 to 40 s timeouts plus 5 s retry sleeps (about 2 min worst case inside a 5-min slot; MeCentral timed out once on 2026-11-07). mod_status is on (Require local) but /server-status is rewritten to the 404 page by the catch-all .htaccess, so there is no scoreboard for bin/admin-perf.php --http or future measuring. Static JS is gzipped on every request: cadcraft.js 198 to 59.5 KB costs 9.0 ms p50 against 0.7 ms for an uncompressed file through the same .htaccess, 147 req/s at c=10 and p99 1,029 ms at c=20 (PERF.16 carries the fix: pre-compressed .br/.gz siblings and an immutable one-year cache). Changes: add the flock, run the probes with curl_multi or cap the total at 60 s, a <Location /server-status> with RewriteEngine Off in this site's vhost. Load floors for the record (c=10, keep-alive, zero failures): health 775 req/s, catalog 303, /status 189, / 80, /apps/cadcraft 58, /use/cadcraft 17.4 req/s at p50 586 ms (its 830 KB page is the throughput ceiling: PERF.2, PERF.3).

– Site and servicesTests and tooling Built · in the lab 1 Owner: the /server-status vhost block and the cron lines in the log (files under /etc/cron.d) docs/0.9-sessions/perf-wave3/
Suggest an item

Anyone can send one; no account and no name needed. The team reads each idea, and the ones we take on appear on this page. Please leave out web addresses.

Top