Process IFCs beyond 2 GBs

[LukasKStavario]

Describe the bug 📝

Hi, I have 2.6 gigabytes IFC and I am unable to translate it on backend in 5 hours.

I am using node.js. I can provide you model.

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

node js backend

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.

[agviegas]

The main problem is that WASM has a hard memory limit of ~2gb, increasing the conversion time of models that surpass it exponentially. We are working on a solution to split down these files to process them by parts, which should make the process time to the same order of magnitude of smaller files

[LukasKStavario]

(y) cant wait for that