Lite's Job History reads only the selected time range, and tab loads read off the UI thread (#5457) by erikdarlingdata · Pull Request #5553 · erikdarlingdata/PerformanceMonitor

Lite's Job History reads filter on run time before the archive dedup, not after it (#5457)

erikdarlingdata

committed

d550dc5

Pin the Job History dedup: the run time filter reaches both scans, and a run archived and live still collapses (#5457)

erikdarlingdata

committed

0b5554b

Lite tabs read the store off the UI thread: the AG, FinOps and plan-viewer calls that awaited it on the dispatcher move into Task.Run, and a census holds Lite/Controls to it (#5457)

erikdarlingdata

committed

b5aa915

The Overview refresh reads the fleet tags off the UI thread, and the census covers the main window (#5457)

erikdarlingdata

committed

9af7479

Lite gets a DuckDB memory limit setting: default 2 GB, 1 GB to 80% of memory, applied at startup (#5457)

erikdarlingdata

committed

6b4768d

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-mem-setting

erikdarlingdata

committed

62e7845

Lite windows read and write the store off the UI thread: Manage Tags, the Database State Overrides editor, the history and drill-down windows, and the census holds Lite/Windows to it (#5457)

erikdarlingdata

committed

f7a25c2

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-windows-offui

erikdarlingdata

committed

f330290

Lite derives DuckDB's thread count from the memory setting: min(8, cores, limit / 256 MB) (#5457)

erikdarlingdata

committed

f305bd9

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-mem-setting

erikdarlingdata

committed

80a679f

Lite's log names the DuckDB memory setting on every DuckDB out-of-memory line (#5457)

erikdarlingdata

committed

ac4e021

Navigation Menu

Repository navigation

Lite's Job History reads only the selected time range, and tab loads read off the UI thread (#5457) - #5553

Lite's Job History reads only the selected time range, and tab loads read off the UI thread (#5457)#5553
erikdarlingdata merged 11 commits into
devfrom
fix/5457-lite-duckdb-oom

Commits on Oct 8, 2026

Lite's Job History reads filter on run time before the archive dedup, not after it (#5457)

Pin the Job History dedup: the run time filter reaches both scans, and a run archived and live still collapses (#5457)

Lite tabs read the store off the UI thread: the AG, FinOps and plan-viewer calls that awaited it on the dispatcher move into Task.Run, and a census holds Lite/Controls to it (#5457)

The Overview refresh reads the fleet tags off the UI thread, and the census covers the main window (#5457)

Lite gets a DuckDB memory limit setting: default 2 GB, 1 GB to 80% of memory, applied at startup (#5457)

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-mem-setting

Lite windows read and write the store off the UI thread: Manage Tags, the Database State Overrides editor, the history and drill-down windows, and the census holds Lite/Windows to it (#5457)

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-windows-offui

Lite derives DuckDB's thread count from the memory setting: min(8, cores, limit / 256 MB) (#5457)

Merge remote-tracking branch 'origin/fix/5457-lite-duckdb-oom' into fix/5457-mem-setting

Lite's log names the DuckDB memory setting on every DuckDB out-of-memory line (#5457)