A number of commands are clearly not multi-threaded. I am working with a very large model created by someone else, converted from mesh to nurb and now using mergeallfaces. I have seen an earlier post (MergeAllFaces - Why so Slow?) about it but it was a while ago and before the mac version was released. The feature request has no comment or progress update.
My question though is a bit more than just mergeallfaces. Even moving a large number (10,000+) objects to a new layer takes a very long time but is only using a single core. Surely, if any process is ideally suited to multithreading, something like that where each object is just having its properties updated without any knock-ons to other objects in the same selection it is just a massive collection of simple, parallel tasks?
Can there just be a wholesale update to make more use of multiple cores that almost everyone now has? I appreciate that some commands might not benefit or even that they might be impossible to multithread but it feels like there is a lot of ‘low hanging fruit’ that could be implemented fairly easily?