This is certainly not related to the size of memory, my friend.
Did you read what I wrote? Completely?
I did write about processor load...
This is certainly not related to the size of memory, my friend.
Did you read what I wrote? Completely?
I did write about processor load...
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
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.
Wow - you sound so very convinced, I think I will try what you suggest.
Thanks.
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
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.
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.
I'm running a brand new iMac Pro (32GB of RAM, Radeon Pro Vega 8GB) and I'm a bit disappointed that Cura doesn't seem to slice models much faster than my old Mac Mini with 8GB of ram, integrated GPU and 4 year old basic hardware.
On my Macbook Air, I was having terrible UI slowness. I started disabling plugins and found that removing the XRAY plugin made a difference.
I have the same exact problem, terrible performance issues render the application unusable.
Disabling some plugins did indeed improve the performance.
But the same situation as the first post described, around 10% of CPU usage and 5GB of free RAM memory...
I'm aware I'm using an old HW (iMac Late 2009, 2,8GHz Core i7, 8GB of RAM and ATI Radeon HD 4850 with 512MB of RAM), but it doesn't make sense...
Recommended Posts
eldrick 65
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.
Link to post
Share on other sites