perf(renderer): resolve timestamps in the scene submission #934
No reviewers
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital!934
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/renderer-single-submit"
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?
Summary
Stacked on #933 (phase 1a). Folds the timestamp query resolve and staging copies into the scene command encoder, so the main scene frame uses one
queue.submitinstead of a render submit plus a separate timestamp submit.resolve_query_setandcopy_buffer_to_bufferafter the final scene timestamp.prev_resolve_subfield.Overlay renderers still submit separately; that is the next phase-1 change.
Verification
cargo fmt --all -- --checkcargo clippy -p orbital_renderer -- -D warningscargo test -p orbital_renderer --no-fail-fastRefs #781.
Smart test results
Result: PASS
Scope: orbital_renderer
Reason: directly changed crates
Elapsed: 53.6s
Workflow run
Overall: 2 tests, 2 passed, 0 failed, 0 skipped
Nextest: 2 tests, 2 passed, 0 failed, 0 skipped
Doctests: no tests reported