⚡ Optimize MicrotubuleTorus rendering with InstancedMesh#27
⚡ Optimize MicrotubuleTorus rendering with InstancedMesh#27jason420247 wants to merge 1 commit intomasterfrom
Conversation
- Refactor `MicrotubuleTorus` to use `THREE.InstancedMesh`. - Use a reusable `THREE.Object3D` for efficient matrix updates in `useFrame`. - Reduce draw calls from ~1080 to 2 for the toruses. 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. |
💡 What: Refactored the
MicrotubuleToruscomponent incomponents/QuantumScene.tsxto useTHREE.InstancedMeshinstead of individualmeshcomponents. A reusableTHREE.Object3Dis used within theuseFrameloop to efficiently update instance matrices.🎯 Why: Rendering hundreds or thousands of individual meshes (360 and 720 in the current scene) is expensive due to the high number of draw calls.
InstancedMeshallows rendering all instances of the same geometry and material in a single draw call.📊 Measured Improvement: The optimization reduces the number of draw calls from approximately 1080 (360 + 720 individual meshes) to 2 (one for each
MicrotubuleTorusinstance). This significantly reduces CPU overhead and improves frame rates in complex scenes.PR created automatically by Jules for task 1626499395424111040 started by @jason420247