Cura 2.4 and Cura 2.5 Beta slow?

[melbo 0]

Hi community,

Not sure if someone else experience the same but Cura 2.4 and Cura 2.5 Beta are super slow on my MacBook Pro 2.2 GHz, 16GB. CPU almost 100% all the time. Any thoughts about it? Would really appreciate it. I used other slicing software before and none of them where so CPU intense like this one.

Best,

Mel

[nallath 1,123]

Slicing is multi threaded these days. This means that it will use more resources if there are any.

If you don't want Cura to use that much resources, disable auto slicing. If more people feel this way, we could also add a force single threaded option, but that would significantly increase slicing time (~ 2x as slow)

[XYZDesignPro 70]

This might be an Apple platform issue? I've found 2.4 and 2.5 BETA faster than any previous versions of Cura.

Win10 Pro, 64 bit, 16GB Ram, Intel Quad Core @ 3.4Ghz.

[Nicolinux 288]

On my Mac Cura 2.4 does not behave weirdly. CPU consumption is normal or else I'd hear it when the spin up.

Sometimes they do but only for very complex models.

[Evavoo 5]

Ive found Cura to work really really slow on desktop imac (16GB ram, latest os), it works a bit better on my macbook pro (also 16GB ram)....

turning off auto slice does help, but really on the imac its pretty much unusable.

S3D is a good alternative slicing software if your on the look-out, it costs $150, but if your going to be doing alot of printing I think it's worth investing in.

[Nicolinux 288]

Cura 2.5 is slower for me than the versions before. Mostly after switching to the layer view and back again.

[XYZDesignPro 70]

Slicing is multi threaded these days. This means that it will use more resources if there are any.

If you don't want Cura to use that much resources, disable auto slicing. If more people feel this way, we could also add a force single threaded option, but that would significantly increase slicing time (~ 2x as slow)

Perhaps the "force single threaded option" as you have suggested, isn't a bad idea. It appears that multi threading has introduced other anomalies into the slicing process, such as not knowing where Cura knows where it left off on the previous layer

From a previous post in April by bagel-orb:

Cura 2.5 definitely handles positioning differently from 2.4. Since Cura 2.5, CuraEngine is using multi-threading to speed up the process. The engine generates multiple layers at the same time. The major disadvantage of this is that the engine doesn't know where the previous layer ended in order to get the point on the inner walls closest to the previous print head location. Instead the engine starts each layer closest to the Layer Start Location.

In addition, I've also experience some strange behavior with support placement in 2.5. Placing support where it is not needed. That's why I continue to use 2.4 for daily production work on my UM3 machines.