⚡ Optimize MicrotubuleTorus with InstancedMesh#63
Conversation
Replaced individual mesh rendering in MicrotubuleTorus with THREE.InstancedMesh
to reduce draw calls and improve rendering performance.
- Implemented InstancedMesh in MicrotubuleTorus component.
- Used a reusable THREE.Object3D for matrix updates in useFrame.
- Added key={count} to ensure proper remounting when instance count changes.
- Set frustumCulled={false} to maintain visibility during animations.
Co-authored-by: jason420247 <44763042+jason420247@users.noreply.github.com>
|
👋 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
💡 What: Replaced individual mesh rendering in
MicrotubuleToruswithTHREE.InstancedMesh.🎯 Why: Rendering thousands of individual meshes resulted in excessive draw calls (~1082 in the baseline scene), significantly impacting GPU performance.
📊 Measured Improvement: Theoretically reduced draw calls from ~1082 to ~4. The optimization uses a single draw call per
MicrotubuleTorusinstance (360 and 720 counts), plus ambient and point lights. Performance is further improved by using a reusableTHREE.Object3Dfor matrix calculations to avoid per-frame allocations.PR created automatically by Jules for task 15974716797949878449 started by @jason420247