Yes, all native on the Mac Studio. I was expecting more, hence the post. Launching Xojo is twice as quick as the iMac, but once in Xojo performance is almost exactly the same as the iMac. Underwhelmed.
My experience is that the speed gain needs to be measured to be ‘seen’
To my brain, the experience of my new M2 machine versus my 2015 intel is very similar.
Buyers remorse
Not quite sure what you mean there. Sorry. iMac i9 with Xojo installed vs new Mac Studio also with Xojo installed performing like for like tasks. Lot of money for no benefit. Tests prove in fact, that the i9 iMac still has the edge over the Mac Studio wih M1 Max cpu.
This really shouldn’t be a big surprise. The single core clock speeds are largely the same. Xojo is a single core app. Until CPUs make a quantum leap in core clock, or Xojo works better with multiple cores, there’s really not much performance to gain.
As Thom says, it really depends on how well an application can take advantage of multiple cores. I’ve been banging on about it for some time as that’s where we’re seeing performance gains on the Mac.
On Wintel, it appears that AMD and Intel are still pushing for single core performance increases and I’ve read good things about Intel’s latest chips. But of course it goes without saying, that Intel remains power hungry processors.
The lack of noise and that the ARM chips don’t make the computers hot alone is very nice. I’ve been doing fractals yesterday. The old Intel MacBook Air would get hot and loud. The M1 Air isn’t bothered by anything.
Not really, according to Geekbench Browser the i9 has a Single Core Speed of 1222 and the M1 Max of 1791 (latest uploaded test results).
There must be some other reasons for the result of David, maybe different macOS or Xcode versions, running background tasks, connected devices etc.
What is Xojo doing after a the progress bar for Cmd-K is finished? For my project it takes about 25 - 30 seconds to compile. Then Xojo meditates with the beachball for 40 - 45 seconds:
I’m sure that app’s that can use multiple cores would be much faster. Sadly I don’t have the time to test other apps, I just wanted to highlight my findings using Xojo and make others aware.
That said, I have a project who process files from a master folder and produce an html code in a TextArea (a Desktop).
For processing nearly 500 sub folders, my 2014 i5 is faster than my 2020 (2021 ?) m1 MacBook Pro.
OK, two or three more seconds on m1: I do not really care, but yes Xojo on m1 is not that fast than Intel CPUs… (on a < 10 seconds whole process time).
Once I set arm compile in the IDE, I had the feeling m1 compile is faster, but the difference (even 2 seconds) is ridiculously small.
I have to say, nearly 40 years ago, I have seen the difference between standard code and optimized code, on an Apple IIGS (GS/OS 4 vs GS/OS 5 on the same machine)… It was tremendous; IMHO worth the time spent. And it was not only from the boot time, usage experience was faster too !