Repository navigation
Help ui_performance
Open UI responsiveness from the application menu to measure interactions in every window. The target is visible feedback within 50 ms.
Measurements are paused by default. Select Resume measurements to start recording.
First frame measures input to a rendered frame in the same window. Ready frame measures a named operation through its rendered result.
Controller phases explain time spent on synchronization, filtering and model updates; they do not measure server readiness unless the operation includes it.
- Measurements stay in memory, retain the last 250 entries, and can be paused, cleared or copied.
- Hidden diagnostics do not rebuild their list.
- Cached search tabs and recent chats retain their lists and scroll position; Refresh still requests current server data.
Each row names the interaction, window, start and end phase, total duration and any controller phases reported by that operation. A slow First frame points to input, binding, layout or rendering work. A slow Ready frame with a quick first frame points to data preparation, a worker, server or model publication after immediate feedback was already visible.
- Clear existing entries and Resume measurements.
- Perform one interaction at a time.
- Repeat it once warm and once after an explicit Refresh.
- Compare first-frame and ready-frame time, then inspect named phases.
- Copy the result together with the matching Debug Log request when server work is involved.
Do not infer a server or GPU cause from total time alone. Measure the real boundary before changing thread counts, cache settings or the graphics backend.
This tool records application-instrumented interactions, not every operating-system, driver or DCC event. A native Maya stall requires Maya profiling and DCC logs as well. Pausing measurement stops new records and does not alter application behavior.
Resume recording, perform an action, then pause and select its row. Arrow keys and Home/End move selection and reveal virtualized rows. Copy exports the complete measurements; Clear resets selection and details. Selection survives resizing. Signing out clears browser measurements and recording state. Browser frame timings bound a paint opportunity using animation callbacks; they do not confirm GPU presentation. Asynchronous handler duration can include waiting; inspect the recorded phases separately.
Native first/ready-frame values include delivery of the presentation notification to the interface thread. They are bounds on visible responsiveness, not measurements of renderer CPU or GPU time. Recording and navigation feedback do not run Python callbacks in the render thread.
To check idle load, open a long report or Help article, wait for loading to finish, then leave it untouched. A settled reader should stop formatting and repainting until content or layout changes. Measure idle separately from opening, scrolling and resizing the view.
TACTIC-Handler · Releases · Issues · English · Русский
English
- Home
- Installation
- Feature tour
- User guide
- Assistant
- Dashboards
- Knowledge Base
- Maya / Shelf
- Plugins / Плагины
Русский
- Главная
- Установка
- Обзор возможностей
- Руководство пользователя
- Помощник
- Дашборды
- База знаний
- Maya / Shelf
- Plugins / Плагины
Development / Разработка