Cura is unusably slow.

[nallath 1,120]

On 7/6/2018 at 2:22 AM, ReggieCarey said:

I started to look at the source code and notice that its utilizing wxPython for a GUI interface. Core committers should run the profiler to find the tight loop.  Likely, its a loop incorporating the GUI event thread.  Is the code busy checking for input from the USB and then checking for events on the event thread?

 

It's not using wxPython. We also regularly check Cura with a profiler. It's not something that's running in a GUI event thread. All of these are kinda the first things you do if something is slow.

As for slowness; It seems to vary greatly from one machine to another. It seems to be some combination of hardware & drivers that cause it, but that makes it freakishly hard to figure out what the hell is causing it.

[LePaul 321]

4gb of RAM?  That's barely running your operating system (and thus the low windows score)

 

 

[eldrick 65]

Windows barely boots in 4GB these days. Add another dozen GB and you will be amazed at how much faster everything runs.

[JCD 28]

Cura is starting in 25 seconds, it's not so bad but longer than other software

 

And windows is starting in 22 seconds

[JCD 28]

here are the system informations I have presently with Cura and Firefox running

 

For the performance Firefox has the worst effect sometimes, with a lot of windows opened in firefox, it can reach 500-600K in memory usage