You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently testing the compression of a specific 3D model using Draco.
Most models are working correctly.
However, when encoding a specific .glb file in the browser using the draco_encoder.js bundle,
it takes over 4 minutes or freezes.
The same file encodes at a normal speed of about 500ms in the Node.js environment using the draco_encoder_nodejs.js bundle.
Why is there a significant difference in encoding time between the web browser environment and the Node.js environment for this specific model?
The model is approximately 13.6MB and has two geometries.
One of them contains position and normal buffers composed of a Float32Array with a length of 842,748.
Could this be affecting the slow encoding in the web browser?
I used the gltf-transform library to conduct the encoding tests in each environment.
Thank you for your response.
The text was updated successfully, but these errors were encountered:
chajooyeong-ndotlight
changed the title
draco_encoder.js encoding speed issue in web browser
Encoding speed issue found when using draco_encoder.js in web browser environment.
Jul 2, 2024
chajooyeong-ndotlight
changed the title
Encoding speed issue found when using draco_encoder.js in web browser environment.
Encoding speed issue when using draco_encoder.js in web browser environment.
Jul 2, 2024
Hello,
I am currently testing the compression of a specific 3D model using Draco.
Most models are working correctly.
However, when encoding a specific .glb file in the browser using the draco_encoder.js bundle,
it takes over 4 minutes or freezes.
The same file encodes at a normal speed of about 500ms in the Node.js environment using the draco_encoder_nodejs.js bundle.
Why is there a significant difference in encoding time between the web browser environment and the Node.js environment for this specific model?
The model is approximately 13.6MB and has two geometries.
One of them contains position and normal buffers composed of a Float32Array with a length of 842,748.
Could this be affecting the slow encoding in the web browser?
I used the gltf-transform library to conduct the encoding tests in each environment.
Thank you for your response.
The text was updated successfully, but these errors were encountered: