Use u64 for change ticks #15683
Labels
A-ECS
Entities, components, systems, and events
C-Feature
A new feature, making something new possible
C-Performance
A change motivated by improving speed, memory usage or compile times
D-Modest
A "normal" level of difficulty; suitable for simple features or challenging fixes
S-Adopt-Me
The original PR author has no intent to complete this work. Pick me up!
S-Blocked
This cannot move forward until something else changes
S-Needs-Benchmarking
This set of changes needs performance benchmarking to double-check that they help
Note
Tracking issue for closed 2022 PR #6327 (alternate approach: #6651)
Original author:
zakarumych
What problem does this solve or what need does it fill?
Avoids the complexity (and runtime perf overhead) of our current looping u32 implementation, at the cost of higher memory usage.
Implementation blocked on configurable change detection.
What solution would you like?
Replace
u32
withu64
for tick values. Maintenance code to guard against overflow should be removed.Downside - requires
AtomicU64
.A workaround should be implemented for when
AtomicU64
is not available on target platform.What alternative(s) have you considered?
See #6651 for context.
The text was updated successfully, but these errors were encountered: