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
Belt Slicer seems to spend a lot of time with a single CPU at 100% pre-processing the model before launching CuraEngine. Is there a hot code path in BeltEngine that needs optimization? Could this benefit from parallelization?
Belt Slicer seems to spend a lot of time with a single CPU at 100% pre-processing the model before launching CuraEngine. Is there a hot code path in BeltEngine that needs optimization? Could this benefit from parallelization?