Files
autodesk/architecture/autodesk-launcher/as-is/performance-profile.md

2.5 KiB

AS-IS performance profile

The startup path performs network-dependent synchronization when installer/update is used, writes generated LISP files, starts a batch and may load 20 assemblies sequentially. No timings were collected; claims about latency, parallelism, cache hit rate, or behavior under unavailable network are UNKNOWN.

Source-level observation Evidence Performance implication Confidence
Installer recursively copies selected catalogs and can delete files/directories All_Serv_Install/Form1.cs copy path filesystem and potentially network traversal; UI blocking behavior requires measurement CONFIRMED
Updater computes MD5/control sums and replaces local files All_Serv_InstallUpdater/Form1.cs repeat hash/read/copy work; no measured count or time CONFIRMED
Bootstrap emits one generated loader command per selected installed catalog P_Serv_Starter/Program.cs sequential startup work grows with selected modules CONFIRMED
OrthoLoader sequentially . _netloads 20 configured modules legacy loading audit 20 managed loads before all functionality is ready CONFIRMED
Repeated load on document/workspace events no complete event evidence cannot assert UNKNOWN

No measured count is claimed for network requests, full copies, UI waits, Process.WaitForExit, Thread.Sleep, or repeated document-level loading. Those are measurement subjects, not observed facts.

Measurement plan (proposed)

Scenario Start End Proposed metrics
Cold start launcher action Ribbon ready elapsed time, files hashed/copied, bytes, NETLOAD count
Warm start launcher action Ribbon ready cache hit, network requests, elapsed time
Offline start launcher action with network unavailable Plant prepared/started valid cache use, retry count, user status
No-update start catalog read launch prepared manifest comparison and file operations
Update start catalog read activation complete staging time, hash time, atomic switch time
Rollback rollback request previous pointer active elapsed time and success/failure
Plugin readiness Plant process created Initialize and Ribbon ready process-start, entry-load, command/Ribbon timestamps

Targets are PROPOSED until baseline data is collected: one entry NETLOAD, zero network assembly loads, zero in-place replacement of active package files, and no repeated full copy on a valid no-update start.