<p dir="auto">I recently updated the three.js files from r58 to r61, and I couldn't believe my eyes. What happen with the performance? I'm loading a single (700k verts) .obj and .mtl file and the time to load it locally extended from 14sek to 1 min 14 sek. Also the frames dropped by 8-10. I tried to use jsonloader, but this just crashes my Chrome.</p>
<p dir="auto">I'm really thankful to all three.js team for their hard work, sweat and tears.</p>
<p dir="auto">Anyone else encountered this problem?</p>
<p dir="auto">We are working on an huge project with thousands of objects, and every object is unique. We load data from a gltf file, and the loader checks if any object is equal to something already created.</p>
<p dir="auto">Disabling the check on the cache <a href="https://github.com/mrdoob/three.js/blob/3665fb0ea0237ebab9798c5847861086782c778d/examples/js/loaders/GLTFLoader.js#L1566">here</a> (<code class="notranslate">return null</code> instead of calling isPrimitiveEqual over thousands of objects) cuts the loading time by a factor of 4, in our case.</p>
<p dir="auto">I know this is a corner case, but would you be interested in an option to disable the cache? My company will sponsor my work on this, because we have to implement it anyway, and makes more sense to do it upstream than keeping our own version of the loader</p>