News for hackers. Stuff that matters.
Re:Introducing the next generation of Mac by qz2 on Tuesday November 10, 2020 @02:27PM (#25050461)
This. I was hitting a wall on RAM instantly at 32Gb.
Re:Introducing the next generation of Mac by snowwrestler on Tuesday November 10, 2020 @03:41PM (#25051629)
Hitting a wall how? The machine stops working properly? Or you see all the RAM allocated in Activity Monitor? Because MacOS aggressively allocates RAM even under a normal workload.
Re:Introducing the next generation of Mac by qz2 on Tuesday November 10, 2020 @03:50PM (#25051717)
Well when you start getting memory pressure you start losing cycles to compressing and decompressing pages which makes everything run like complete shit.
Re:Introducing the next generation of Mac by jiofih on Wednesday November 11, 2020 @02:04PM (#25061641)
That’s not how MacOS works. It “keeps the pressure on” so to speak to try and have as much in-memory before you need it. Have you experienced actual issues with specific software?
Re:Introducing the next generation of Mac by conductr on Tuesday November 10, 2020 @02:50PM (#25050848)
Out of curiosity, doing what??
Re:Introducing the next generation of Mac by qz2 on Tuesday November 10, 2020 @02:57PM (#25050967)
IDE + VMs + office + slack + zoom etc
Re:Introducing the next generation of Mac by conductr on Tuesday November 10, 2020 @03:04PM (#25051078)
Blows my mind, I do most of the same on a 2013 MacBook Air with only 8GB RAM. I’ve never had a perf hiccup unless I try video editing or gaming. But I just don’t really have a want to do those things, hence why I’m still getting by on this thing. I was going to upgrade once for the hell of it but all the keyboard issues kept me seated.

I expected you to say you did something with graphics/media. I guess the VMs could be the difference. I don’t use. But I have 100 chrome tabs open at most times lol.

Re:Introducing the next generation of Mac by selsta on Tuesday November 10, 2020 @03:24PM (#25051389)
All these things work with 8GB RAM. macOS uses all available RAM aggressively, so if you have 32GB RAM it will appear as what you are doing requires 32GB RAM, which is not the case.
Re:Introducing the next generation of Mac by qz2 on Tuesday November 10, 2020 @03:32PM (#25051508)
No they don't. It starts compressing pages when the memory pressure goes up and then it starts running like dog shit.
Re:Introducing the next generation of Mac by nottorp on Tuesday November 10, 2020 @04:36PM (#25052301)
On my machine, if it goes more than 5G into swap it starts to become less responsive.

It really depends on your usage patterns. VM abusers and people who need to keep an eye on more than one project at the same time (as in multiple IDEs) can't do with 16 Gb.

And please don't tell me to start closing software, I'm willing to pay for more ram to have everything handy. Except... I can't.

Re:Introducing the next generation of Mac by quicklyfrozen on Tuesday November 10, 2020 @03:32PM (#25051505)
Right now I have 6GB for VMs (for ~12 docker containers) and 8GB for various IDEs and editors. Probably typical for those on my development team. Surprisingly Chrome isn't even the top ten for memory footprint on my laptop.

So far 16GB has been fine on this 2017 MacBook. Wouldn't turn down 32 though :-)

Re:Introducing the next generation of Mac by matsemann on Tuesday November 10, 2020 @04:42PM (#25052375)
You have reduced performance, you're just accustomed to it.
Re:Introducing the next generation of Mac by conductr on Tuesday November 10, 2020 @05:11PM (#25052731)
Could be true. But I get instant feedback from all apps, so what's the measure of "reduced performance" that would matter? I'm actually curious, if nothing lags, would I notice a difference by upgrading?

My view into your comment is that you think I'm used to the lag. That's not the case. It's not my only device just my only Apple laptop. My newest device, a iPhone 12 Pro, is an upgrade from my 6s that I surely noticed and knew I would. I had been frustrated by the 6s for a while but held out for 5G.

Re:Introducing the next generation of Mac by nicoburns on Tuesday November 10, 2020 @03:54PM (#25051775)
Yeah, I found running all my dev environments in Docker/VMs made everything too slow. So I've just installed everything natively and have my own little docker-compose style runner to simplifying running our in-house microservices. I would definitely appreciate decent Docker performance, but it was actually surprisingly painless to set this up.
Re:Introducing the next generation of Mac by Bahamut on Tuesday November 10, 2020 @03:27PM (#25051429)
I don't see this issue having IntelliJ, Xcode, VSCode, Slack, Discord, and more open simultaneously on a continuous issue...with 16 GB of RAM.

I'm somewhat impressed by some of these stories about RAM usage - what are people doing?

Re:Introducing the next generation of Mac by mike_ivanov on Tuesday November 10, 2020 @07:34PM (#25054121)
RStudio, interrogating a ~0.5 billion record dataset. A 192G Ram machine.
Re:Introducing the next generation of Mac by jiofih on Wednesday November 11, 2020 @02:07PM (#25061674)
I did some benchmarking on that public taxi rides dump (~600m records) and could run through it all in under 15 seconds directly from SSD. No way in hell your CPU will keep up with anything close to memory bandwidth or beyond 3GB/s.
Re:Introducing the next generation of Mac by jiofih on Thursday November 12, 2020 @08:30AM (#25069614)
Using Clickhouse btw.
Re:Introducing the next generation of Mac by qz2 on Tuesday November 10, 2020 @03:30PM (#25051477)
4 node Kubernetes cluster, vagrant build environment.
Re:Introducing the next generation of Mac by Macha on Tuesday November 10, 2020 @03:59PM (#25051823)
Debugging Ember or Spring applications.