Actually, someone did a benchmark and equated the 800 MHz RPi CPU performance to that of an Intel Pentium II 300 MHz from back in 1997. That is almost 20 year old technology.
The code design for CW does not appear to be optimal. Perhaps it is .NET or whatever they used to compile it, but it is known to not properly handle its internal memory management and as soon as the computer is forced to swap memory to the file, the performance goes into the toilet because it appears to be tightly coupled with the file system. Almost like a threading problem or a wait on resources. Keeping all of those slices in memory or doing on-demand slicing is too expensive, particularly on very large STL files. That is why closing CW and reopening it improves performance when it starts to slow down.Statistics: Posted by rkundla — Thu Mar 03, 2016 1:18 pm
]]>