wim
(Wim Dekeyser)
September 15, 2016, 10:39am
2
It will do its best to multithread, yes.
“[…] ALL the performance […]” - that’s pushing it…
There have been many discussions on the topic - here are a few hits:
Although it is true that Rhino does not use multi-threading for most operations at the moment, we recognise that if we’re to make use of the hardware people buy this needs to change. As we move forward, .NET will become a more important part of our development and the Task Parallel Library has some pretty good stuff for easily multi-threading stuff.
Although I hesitate to make a promise, it’s certainly a good bet that -over time- Rhino will become more and more multi-threading capable. If you’r…
Scripting is a linear operation and not easily threaded (since the next thing to be scripted is dependent on the current one finishing).
I’m not sure how you measure the “size” of a script. But the size has no correlation with the speed of execution.
We are always in the process of doing this…
Try to keep in mind that multithreading is not the holy grail of performance. Certainly some features can and will benefit from multithreading. But many operations, that appear to be good candidates…