Try to run the : webgl_instancing_performance I found that when use the ThreeJS to render stuff no matter if i just render in native drawcalls or merge them to render once, or use instance rendering, the FPS is almost that same, sometimes the native mode is even faster with chrome + any integrated …

Merge or Use instance and Native render make no difference with Chrome plus Integrated Graphics Card

donmccurdy February 19, 2020, 4:43pm 19

I actually wasn’t really expecting any major FPS difference between instancing and merged, just a very different memory footprint. What do you see at 50k instances? I’m curious if that’d be consistent across different mesh sizes and devices.

InstancedMesh - does it require a specific feature that not all GPUs have?

Topic		Replies	Views
Is it strange? threejs showcase "webgl_instancing_performance" Questions performance	6	538	August 1, 2022
Rendering thousands of objects results in low FPS but also low GPU usage Questions performance , instanced-mesh	4	2839	July 9, 2022
Benchmark results for Chrome, Firefox, IE show massive difference. Why? Questions performance	5	1136	April 20, 2020
WebGPU performance significantly slower (rendering non-instanced geometries) Questions performance , webgpu	7	1943	September 8, 2023
Three.webgpu.js with "forceWebGL": WebGL in Chrome slower than WebGL in Firefox Questions webgl , chrome , webgpu , firefox , slow	0	41	May 14, 2025

Merge or Use instance and Native render make no difference with Chrome plus Integrated Graphics Card

Related topics