Investigate performance issues in tables
Scrolling through tables leads up to 30% CPU usage
- check global state / table properties logic for potential bottlenecks
- can a global state update via
Action::Updatebe prevented at all?
Scrolling through tables leads up to 30% CPU usage
Action::Update be prevented at all?