Performance timing log spam #1019
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital#1019
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Primarily: performance logging (timings and such) should be a toggle in Debug-UI.
However, maybe data should be written into a file (possibly even into a table like CSV).
This would clear up the log a lot. Not sure if we can write to a file easily on Android/iOS/Web though and then pull/retrieve it.
Implemented in #1024. The Performance panel now has a Log FPS, timings & cache counters toggle backed by
PerformanceLogConfig. Periodic FPS, TIMING, and PERF lines are off by default and only emitted when enabled. The one-second window resets while disabled, so enabling logging does not dump a backlog. CSV/file capture remains a possible future enhancement; the runtime toggle is done.Expanded in #1026. The Performance panel now has separate console and CSV switches. CSV capture writes
Logs/performance.csvwith elapsed time, FPS, frame delta, all timing stages, and cache/creation counters. Desktop and iOS (Documents, with file sharing enabled for new projects) are directly retrievable; Android remains app-internal for now, so debug builds needadb pull. Native mobile share/save is still a follow-up.