Roast my config. I’m probably gonna checkout this MacBook tomorrow. It’ll be a big step up from my M1 Pro I’m sure.
@mattcomi why so much ram?
@mattiem future proof for the next 5-6 months.
@mattcomi ram is so important if you are running virtual machines. When I used to do that, there was never enough…
@mattiem nah my honest answer is just I want to much much much more than I currently have on my M1. Xcode is horribly slow and I’m constantly playing janitor with running apps to free up RAM.
@mattcomi ohh that’s interesting to hear! I’ve been trying to figure out if ram will help with the development experience there.
@mattiem @mattcomi I know someone who is putting DerivedData into a RAM disk and claims that this is a great idea. I think it could be.
@helge @mattcomi this would imply that disk speed is a major bottleneck here, which I find slightly surprising but maybe I should not…
@mattiem @mattcomi The SSDs are *very* fast now, but RAM is still much, much faster.
@helge @mattcomi yes I am aware of this
@mattiem @mattcomi My concern would be that the speed is eaten up by all the FS layers, but who knows. Sole reason I consider a 48+ machine tbh 😬
@mattiem @mattcomi “this would imply that disk speed is a major bottleneck” I think it actually is for Swift targets, they are not multi core constrained but disk plus single core perf.
The only time I see my CPU exercised is when compiling swift-nio-ssl, ie BoringSSL, which sucks all cores available.
@mattiem @mattcomi That’s separate to you building the compiler, which is C++ and should scale to the available cores.
@helge I don’t know if the language matters here as much as the build system being used? The “compiler project” includes a huge amount of swift code, in the standard library for example.
@mattiem It does because Swift compilation units are not self contained, unlike C units