Technology

60292 readers

3259 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

477

Apple keeps flogging 8GB of RAM for its Mac computers but it's still a dead horse (www.pcgamer.com)

submitted 8 months ago by [email protected] to c/[email protected]

314 comments fedilink hide all child comments

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

[–] sugar_in_your_tea 1 points 7 months ago

A couple things to start:

I don't need x86 compatibility - we run native aarch64 on M-series Macs, and x86 on older Intel macs; prod is x86, but we're considering moving to aarch64
our app is more memory intensive than CPU intensive - basically a bunch of Python microservices

That said, after some research into colima, it looks like it wins on I/O. So if you workload is relatively heavy on I/O, then it's probably worth trying out.

My issue is memory. I just need so many Python interpreters running Flask, FastAPI, and Django (we use all three). On macOS, I need to reserve the memory for the VM, which means I need to balance how much I can run vs what other stuff I want to run on my system. On Linux, there is no VM, so I benefit from all of the disk caching that the kernel does and can get a much better experience, even when running a lot of services (most of those services are idle most of the time).

So switching to colima probably wouldn't solve my problem, but maybe it would solve yours.