Even on Windows things are not plain sailing. An example I am interested in (not professionally but for a house renovation I am doing) is using the Pro version of Sketch-up which is a 3D program which can do architecture, and perhaps the V-Ray plug in which output can provide realistic picture simulation views.
With Windows evidently, firstly Sketch-up is single threaded, so single thread performance is where its at for the CPU ... and then, there is also a hybrid way it works, where it also uses the GPU, but .... the GPU needs to be an Nvidia to work well. So Windows isn't so simple.
Then with the M processor, Sketchup had it working in Rosetta for ages ... now, its working native ... but its not utilising the GPU part of the processor, from what I have been able to find out. And the V-Ray side initially did not work, with some direct calls having to be made via the Unix window - terminal screen to get it to work ... via Rosetta. Later maybe it'll use the CPU correctly, and maybe the GPU side.
Perhaps though, if the various parts of the software do go native to the CPU and the GPU part of the processor, then such software houses will have less work to do, as once they get the work done, updates may be quite simple.
I can see the sense in Apple having introduced the notebook M Pro and Max before the Mac Pro desktop(s). What point is there in them for some, if the software hasn't yet taken advantage of the new Apple single memory and on chip powerful GPU architecure?
I looked to in Australia at an MSI notebook (& others) with a 3080 GPU - and to choose the 64 GB RAM version instead of 32 GB for the notebook, the memory cost increase was about double Apple's 64 GB RAM price increase from 32 GB.
With Windows evidently, firstly Sketch-up is single threaded, so single thread performance is where its at for the CPU ... and then, there is also a hybrid way it works, where it also uses the GPU, but .... the GPU needs to be an Nvidia to work well. So Windows isn't so simple.
Then with the M processor, Sketchup had it working in Rosetta for ages ... now, its working native ... but its not utilising the GPU part of the processor, from what I have been able to find out. And the V-Ray side initially did not work, with some direct calls having to be made via the Unix window - terminal screen to get it to work ... via Rosetta. Later maybe it'll use the CPU correctly, and maybe the GPU side.
Perhaps though, if the various parts of the software do go native to the CPU and the GPU part of the processor, then such software houses will have less work to do, as once they get the work done, updates may be quite simple.
I can see the sense in Apple having introduced the notebook M Pro and Max before the Mac Pro desktop(s). What point is there in them for some, if the software hasn't yet taken advantage of the new Apple single memory and on chip powerful GPU architecure?
I looked to in Australia at an MSI notebook (& others) with a 3080 GPU - and to choose the 64 GB RAM version instead of 32 GB for the notebook, the memory cost increase was about double Apple's 64 GB RAM price increase from 32 GB.
Last edited:
