Compilation time - Windows vs. Mac
-
@Oli-Ullmann Because Xcode is crap.
-
@Oli-Ullmann It's the other way around for me. Windows perceived 10 times slower, same machine. Especially the linking process.
-
-
@d-healey
OK :-) -
@d-healey VMware on a M3 studio mac
ducks & runs -
@Morphoice That's probably the cause of the issue, it's having to emulate an Intel CPU so you'll probably lose a lot of performance.
@Oli-Ullmann Are you using a VM or are you using two separate systems?
-
@d-healey
I have a separate Mac and a separate Windows PC. -
@Oli-Ullmann What CPU/RAM in each? Both SSDs? Compiling with same number of threads?
-
Both have SSDs.
Mac config:
MacBook Pro (End 2019)
2,4 GHz 8-Core Intel Core i9
32 GB RAMPC config:
Intel i5-6500 CPU @3.2 GHz
16 GB RAMOn the paper it looks like the Mac has more power.
Where can I see how many threads are used for compiling, or where can I set this? Do you know that?
-
@Oli-Ullmann said in Compilation time - Windows vs. Mac:
On the paper it looks like the Mac has more power.
Sure does. Is it the compiling that is taking the time or the linking?
@Oli-Ullmann said in Compilation time - Windows vs. Mac:
Where can I see how many threads are used for compiling, or where can I set this? Do you know that?
I'm not sure, I don't use VS or Xcode much, I tend to build from the CLI. However the compile scripts that HISE generates should set the max number of threads based on your CPU - or maybe that's just in my fork...
From the CLI for xcode I think it's the
--jobs
argument. I can't remember on Windows but probably--threads
. -
@d-healey
Next time I'll see if it's the compiling or the linking that takes so long. I'll also try to find out how many threads are being used and then report back here. Thanks to you! :-) -
@Oli-Ullmann usually the linking is ridiculously long