Jump to content
Ultimaker Community of 3D Printing Experts
Bossler

Cura Performance on Mac

Recommended Posts

I've been using Cura 3.1 and now am using Cura 3.2 on a MacBook Pro Retina.

This machine is equipped with an iCore 7 / 2.5-3.7GHz main CPU plus an AMD Radeon R9 M370X GPU.

I have checked that Cura uses the Raedon GPU and it does.

 

But the performance when slicing and - especially annoying - dealing with layer preview after slicing a bit more complicated models is really bad, sorry.

 

There has to be some substantial design flaw in the software because the system described above is quite capable.

 

When looking at this picture:

5a7a3dc75ca03_Bildschirmfoto2018-02-07um00_22_44.thumb.png.337b82bae689b7d847024ab5f223268f.png

 

...you see that Cura is not even using a third of the available computing power, even during slicing!

With that kind of computing demand to the system I doubt that the processor is going into "high speed mode"...

 

After slicing's done and when one works with the layer preview, CPU-usage is typically around max. 10% -
and Cura is very, very laggy then...

 

So you friends at Ultimaker may would like to go into some performance review and optimize +

Cura - which is certainly the best companion for Ultimaker 3D-printers out there at current.

I certainly would highly welcome such an effort.

As possibly a lot of other users would do as well.

Share this post


Link to post
Share on other sites

I run Cura 3.1 on an iMac, and have no such problem. However, I have 24Gb installed.

How much memory is in your Mac Book?

Oh, and BTW, you can turn off automatic slicing, which will allow your to change the settings without the lag of slicing for each change.

 

Share this post


Link to post
Share on other sites

Strange, i use a old (ancient mid 2012) macbook air, I5 1.8Ghz with 4Gb ram, and the speed is acceptable. 

Can we do some kind of benchmark? Slicing same object with same settings and time this?

Edited by RudydG

Share this post


Link to post
Share on other sites

Yes, Bossler, I did read what you wrote.
You didn't mention memory size, what version of OSX you are using, or a number of other things that could be relevant. The performance issue you seem to have is almost certainly something about your system and its software, and not Cura's fault, as many other Mac users, myself included, don't have any performance issues.
If Cura is only using 10% of the processor time, you may be looking at a task that only runs as a single thread (1/8 of total available processor time), or there may be some other bottleneck in your system slowing it down.

Again - there are many other Mac users who don't have any performance issues with Cura. Try creating a new partition, install a clean copy of OSX in it, and try Cura running from it - I'll bet you won't see a performance issue.

Share this post


Link to post
Share on other sites
15 hours ago, eldrick said:

The performance issue you seem to have is almost certainly something about your system and its software, and not Cura's fault

 

I am not quite as sure of that as eldrick. Something that can also still play a role is the Cura configuration. It could be for example that the Custom FDM Printer still performs substantially slower than eg an Ultimaker 2+. I think it is a combination of factors, which is why it is so hard to track down.

 

Having said that, it would be nice to know if starting from a clean copy of OSX changes anything.

Edited by ahoeben

Share this post


Link to post
Share on other sites

The only performance issue I've seen on mac with recent Cura versions was the horribly slow load time due to the plethora of printer configs beling loaded. 
That one was easy to deal with by removing all the never-gonna-use printer configs from the executable.

Share this post


Link to post
Share on other sites
13 hours ago, eldrick said:

The only performance issue I've seen on mac with recent Cura versions was the horribly slow load time due to the plethora of printer configs beling loaded. 
That one was easy to deal with by removing all the never-gonna-use printer configs from the executable.

That has been fixed in the 3.2 version by only loading the printers you need.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

Terms of Use Privacy Policy