Rendering and Performance
FreeKeep thousand-item boards responsive.
FenSight keeps large boards responsive by reducing decode cost, drawing the right level of detail for the current zoom, and switching dense boards onto virtualized surface rendering. The defaults favor stability on fresh installs while still allowing detail to be raised when hardware has room.
LOD tiers
Board rendering chooses a level of detail from the item's physical-pixel size in the current viewport, including DPI. The goal is to avoid decoding or drawing more bitmap detail than the user can see.
Ingest and rendering
Large imports are handled as a staged ingest path: cheap item/header work can populate the board first, while decode workers fill in thumbnails and richer media detail afterward. On very large boards, FenSight can proactively choose surface-only visuals before every item has a full WPF container, reducing pressure on GDI and the UI thread.
- LimitImageDecodeSize defaults to true and MaxDecodeDimension defaults to 2048, so fresh installs downscale oversized images during decode.
- IngestPerformanceMode defaults to "Balanced"; Maximum uses 2-64 workers at normal priority, Quiet uses up to one quarter of cores below normal priority, and Balanced uses about 60% of cores with a floor of 2.
- DeferThumbsOnLargeBoards and CacheVideoAndDocumentThumbnails default to true, so thumbnail work can be postponed and reused instead of blocking navigation.
- UseVirtualizedBoardSurface and UseVirtualizedBoardSurfaceInput default to true, allowing dense boards to render and hit-test through the board surface path.
Performance controls and defaults
Virtualized surface behavior
For incoming large boards, FenSight estimates the projected item count before committing to heavyweight visuals. If the projected count is at least 400, or if safe graphics mode is active, it enables virtualized board surface rendering and virtualized input. The same enforcement path disables the regular item metadata overlay so that per-item text does not add cost during the most constrained mode.
- MainWindow constants define LodThumbMax 256, LodMediumMax 1600, LargeBoardThumbMax 128, and HugeBoardThumbMax 64.
- Thresholds are based on physical pixels, so monitor DPI affects when Thumb, Medium, and Full imagery are selected.
- Performance HUD / ShowBoardPerfOverlay is the setting name for board rendering diagnostics.
Connected guides
Follow these related pages when the workflow crosses into setup, search, organization, export, security, or another board-level system.