Performance modes, rendering sharpness and the FPS meter
The Performance section sets a few rendering knobs at once through three presets (Performance, Balanced, Precision) or lets you set them by hand in Manual. The Rendering sharpness cap decides how many canvas pixels the charts draw; Ctrl+Shift+F shows a frame-rate meter to measure the result.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Settings → Performance
- Default mode
- Balanced: 1.5× rendering, 3 months of crypto candles, globe spin on, motion on
- FPS meter
- Ctrl+Shift+F toggles it; the choice is remembered between launches
- Mode rule
- Editing any preset value by hand switches the mode to Manual
What it does
A mode is a preset: choosing one writes three values into the app-settings store (rendering cap, globe auto-spin, reduce motion) and one into the chart store (crypto deep-history depth), then imposes nothing further. If you later change one of those values by hand, the mode label switches to Manual so it always reflects what is true rather than what was clicked once. Manual itself writes nothing.
Rendering sharpness is a cap on the device pixel ratio used by the canvas renderers. At 1× a HiDPI screen draws half the pixels per axis (fast); at 2× every screen pixel is drawn (razor sharp, heavier). The footprint renderer reads this cap outside React each frame. The dashboard background applies its own limits on top: its frame rate is capped near 30 per second, its backing store is bounded to 4 megapixels with a floor at 1×, and it stops completely when the window loses focus or leaves view.
Settings
| Setting | Default | What it changes |
|---|---|---|
| Mode: Performance | — | 1× rendering, 30 days of crypto candles, globe still, reduce motion on. For laptops and busy machines |
| Mode: Balanced | Selected by default | 1.5× rendering, 90 days of candles, globe spin on, motion on |
| Mode: Precision | — | 2× rendering for 4K screens, 180 days of candles, globe spin on, motion on |
| Mode: Manual | — | Your own values below; set automatically when a preset value is edited |
| Rendering sharpness | 1.5× | Cap on the canvas pixel ratio: 1×, 1.5× or 2× |
| Crypto history and profiles | 3 months | Binance Spot / Perp candles and volume at price kept on disk: 1 week, 1 month, 3 months or 6 months. Choosing a value that differs from the preset switches to Manual |
| News globe auto-spin | On | The globe keeps turning on its own on the News page |
| Reduce motion (General section) | Off | Part of the presets: Performance turns it on, the others off |
The FPS meter
Press Ctrl+Shift+F anywhere in the connected app to show a small status strip; press it again or click ✕ to hide it. The state is saved so the meter comes back on the next launch if you left it on. It shows three numbers: the frame rate smoothed over one second, the worst frame time of that second in milliseconds (the number that decides how smooth it feels), and the detected refresh rate of the screen, measured once from the median interval of 60 frames so a single slow frame at start does not turn a 170 Hz screen into 90 Hz.
The colour of the FPS value is judged against the detected refresh rate, not against 60: green at 92 % or more of the screen rate, amber from 70 %, red below. While the window has no focus the meter keeps measuring and, when you come back, shows the average and minimum frame rate of that background period. If the OS asks for fewer animations it adds an animations OFF (Windows) note, because the dashboard background is deliberately frozen in that case and looks like a bug otherwise.
The meter costs one subtraction and one comparison per frame and one React render per second, so it does not distort what it measures.
How to use it
- Start from Balanced. Switch to Performance on a laptop or when several chart windows run at once; switch to Precision on a 4K screen where 1.5× looks soft.
- Measure before changing: open the FPS meter, watch the worst-frame value while scrolling a busy footprint, then lower the sharpness cap or the history depth and compare.
- The crypto history depth also decides how far back profiles can be built; the hint notes that 6 months needs a chart grain of 30m or higher.
Limits and pitfalls
- The sharpness cap is a ceiling: a 1× screen never draws more than 1× whatever the setting.
- The FPS meter reads the window's frame loop; it does not measure the Rust backend or the data feed.
- Reduce motion affects interface transitions, not chart rendering; the dashboard background freezes on the OS accessibility setting, not on this switch.
Related pages
This page in other languages
Frequently asked questions
- Why did my mode change to Manual by itself?
- You edited a value that a preset controls: rendering sharpness, globe auto-spin, reduce motion, or the crypto history depth. The mode reports what is true, so it stops claiming a preset it no longer matches. Pick a preset again to restore its values.
- Which mode should I use on a 4K monitor?
- Precision sets the 2× cap so text and cells are drawn at full screen resolution. It is the heaviest option; if the FPS meter shows red, go back to Balanced.
- How do I show the frame-rate counter?
- Press Ctrl+Shift+F. The strip shows FPS, the worst frame time in ms and the detected screen refresh rate, plus a background summary when the window regains focus.