Apple

17499 readers

47 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:

No NSFW Content
No Hate Speech or Personal Attacks
No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago

MODERATORS

MichelleG

RoyalEngineering

thisisdee

Question for M2 Mac Studio owners: How did you choose your specs? (self.apple_enthusiast)

submitted 1 year ago by cantankerous_cashew to c/apple_enthusiast

7 comments fedilink hide all child comments

Title says it all. I'm planning to get an M2 Mac Studio soon. Personally, I'm still coming to a decision on the following SoC & RAM options:

SoC:

M2 Ultra with 24-core CPU, 60-core GPU, 32-core Neural Engine
M2 Ultra with 24-core CPU, 76-core GPU, 32-core Neural Engine

RAM:

128GB
192GB

To current M2 Studio owners, how did you choose your specs and why? Also could you comment on real world performance with regards to your workflow(s)? Thanks! :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 1 year ago (4 children)

Developer here. Completely depends on your workflow.

I went base model and the only thing I regret is not getting more RAM.

Speeds have been phenomenal when there binaries are native. Speeds have been good when the binaries are running through Rosetta.

The specs you’re wavering between are extremely workflow specific. You know if your workflow requires the 16 extra GPU cores. You know if your workflow requires another 64 GB of RAM.

[–] [email protected] 1 points 1 year ago (2 children)

What use case would you need more than 32gb RAM?

[–] [email protected] 3 points 1 year ago

I spin up a lot of Docker containers with large data sets locally.

load more comments (1 replies)

load more comments (2 replies)