question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Loading optimization

See original GitHub issue

This issue refers to how fast the scenes load. In other words, how fast can we parse an IFC file. Check out https://github.com/agviegas/IFC.js/issues/33 for the related geometry optimization issue.

I have implemented web workers to allow for “multithreading”. Here’s a link to my fork. I have documented my thoughts here and here.

TL;DR:

https://user-images.githubusercontent.com/31659443/106889012-b0864480-66e7-11eb-992d-b5c7cdc58386.mp4

The next step is to figure out how to implement my (or a similar) solution into this project. There are many ways to do this.

I suggest we/you release the first version of IFC.js and THEN implement web worker support. Yes - performance is an important factor. But, I think it’s more important to support the most useful IFC2x3 classes.

Anyways, that’s just my thoughts. I’m open to suggestion and I encourage others to experiment with this as well.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:3
  • Comments:7

github_iconTop GitHub Comments

1reaction
agviegascommented, Mar 8, 2021

I’m closing this issue for now, as the main responsible for optimization now are both web-ifc-three and web-ifc. Feel free to drop new ideas there to make this even faster!

1reaction
andrewisencommented, Feb 16, 2021

I noticed that my multi-web-worker example didn’t perform as well with the latest changes (e.g. https://github.com/agviegas/IFC.js/commit/b41d41b60188d255ef0da7b9470200060a148b14, https://github.com/agviegas/IFC.js/commit/453640866ed823c91913a35d75026e36d2257dd0, https://github.com/agviegas/IFC.js/commit/d92e8f87211f87d798c10b853f446c0ee900a579).

There is a time penalty for starting an additional Web Worker. My guess is that the parser is so much faster now that there’s no performance gain to be made. This might be different for large (>200MB) IFC files.

I will experiment with this some more 😄

Read more comments on GitHub >

github_iconTop Results From Across the Web

Load Optimization and Shipping Less Air - ORTEC
Empty space is a huge problem in logistics. This article explores how load optimization can help you tackle this problem and ship less...
Read more >
The Significance of Load Optimization - Nefab
When optimizing your packaging and shipments, you want to make certain you're not transporting too much air. By that it means that you...
Read more >
Containers Loading Optimization with Python | by Samir Saci
As you have limited influence on the market price, your only solution is to improve your loading capacity to save space. I. How...
Read more >
Load Optimization Problem - Medium
The purpose of packing problems is to determine the optimum way to pack a collection of items with varying sizes into containers with ......
Read more >
Fast load times - web.dev
Techniques for improving site performance. Collection cover image. Overview. When you're building a modern web experience, it's important to measure, optimize ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found