Performance

Measure the right values

The editor reports mesh count, vertices, triangles, materials, textures, animation clips, file size, and live draw calls. Point-cloud geometry may have many vertices without triangles.

Rendering checklist

• Cap dpr on mobile and high-density screens.
• Reduce draw calls before focusing only on polygon count.
• Compress textures and choose appropriate dimensions.
• Avoid whole-model normal helpers outside development.
• Disable shadows when they do not materially improve the shot.
• Use one environment rather than many dynamic light sources where possible.
• Pause sequences and effects when the viewer is off-screen.

React guidance

Per-frame values are applied inside React Three Fiber's render loop. Do not lift every frame into React state. Use onSequenceFrame for occasional UI synchronization, not as the primary animation engine.

Disposal

The viewer clones the loaded scene so material overrides do not mutate shared loader cache state. Cloned geometry, materials, and textures are disposed on teardown.

Large point clouds

Point size, opacity, and additive effects can cause substantial overdraw. Test fill-rate cost, especially when particles cover the whole screen.

Profiling

Use browser performance tools, the Three.js renderer info object, and real devices. A desktop development machine is not a representative mobile benchmark.