⚡ Optimize EntityManager::getTransforms vector usage#26
Conversation
Replaced clear()+push_back() with resize() and direct index access in EntityManager::getTransforms. - Benchmarks show ~17% improvement in function execution time (0.70s -> 0.58s for 10000 entities x 10000 iterations). - Eliminates capacity checks and size increments per element. - Retains the benefit of caching the vector (no heap allocation after steady state).
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
This PR optimizes
EntityManager::getTransformsto further reduce overhead.Changes
cachedTransforms.clear()andpush_back()loop withcachedTransforms.resize()and direct assignment.Performance
This ensures that the per-frame transform gathering for TLAS updates is as efficient as possible.
PR created automatically by Jules for task 8125400687821193897 started by @TECHNICANGEL