KhronosGroup / KhronosGroup/glTF-Compressor

Slow to run in Chrome?

Open
#11 4 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
JavaScript
Stars
83
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Feeding this back from myself and the 3D team at my work, we all find that the compressor runs very slow on the web, is there any plan to do a Windows/Mac/Linux build of this that runs local?

The wait times for compression can feel very long and Chrome on Windows 10/11 can often freeze for a few minutes running it as the only open tab.

I have used similar compressors such as gltfpack: https://github.com/zeux/meshoptimizer/releases and Needle Tools which run much faster natively https://needle.tools/

We are testing with models from the GLTF samples repo such as DamagedHelmet and BarramundiFish so these aren't big test models.

Just wondering if running on the web is what is causing the performance bottlenecks?

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the slowdown in Chrome on Windows 10/11 using DamagedHelmet and BarramundiFish from the glTF Samples repository, comparing the web compressor with the referenced gltfpack and Needle Tools. Profile the compression path to determine whether the browser is the bottleneck; the issue needs a decision on native Windows, Mac, and Linux builds and a measurable performance target before implementation can start.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop, performance, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.