Why the number matters
The GPU draws triangles very quickly. What is often expensive is getting there: for each call the browser prepares state, binds textures and buffers and hands over commands. MDN therefore recommends batching draw calls into fewer, larger ones; 1,000 sprites, for instance, ideally in a single call [1].
A product with 400 individually modelled screws, each with its own material, can therefore be slower than a model with twice the triangles in a few parts.
Measuring
In three.js the renderer reports the number of draw calls per frame directly (renderer.info.render.calls) [2]. That figure belongs in every performance budget alongside triangles and file size.
Fewer draw calls: the levers
- Merge meshes: parts that never move separately and share a material become one mesh. The gltfpack tool can merge meshes for this [3].
- Share materials: identical surfaces use the same material rather than copies.
- Texture atlas: several textures in one image allow larger batches [1].
- Instancing: draw many identical parts in one call [4].
The trade-off in a configurator
A configurator needs to address parts individually: recolour, swap, hide, explode. Merging everything into one mesh prevents that. The skill lies in merging only as far as the interaction allows and handling the rest with instancing.
In the spiral stair configurator (example configurator, fictional product) all treads and all balusters are each drawn as one instanced mesh rather than dozens of separate parts. The 3D product viewer page covers performance on product pages.