5 ms·
I dunno, working with M1 daily I struggle with resource contention and slow py/js builds. I'd love something faster when work provides me with updated device.
by pylotlight 1y ago
I dunno, working with M1 daily I struggle with resource contention and slow py/js builds. I'd love something faster when work provides me with updated device.
- dontdoxxme 1y agoSounds like you need to spend some time optimising your build. Faster hardware just makes developers lazy. I'm still on an M1 and it's fine, although I do have 32GB.
- dangus 1y agoTo be fair, for all you know they’re building something pretty crazy that justifies high resource consumption. Faster hardware doesn’t exclusively make developers lazy, it also opens up capability.
- steve_adams_86 1y agoThat's the thing. It's not a trivial project. I've already put a lot of time into optimizations and the returns are diminishing now.
- dangus 1y agoIn the age of AI it seems wild to blame developers for being “lazy” and needing more resources. Like, if I were buying a new workstation right now, I’d want to be shelling out $2000 so that I could get something like a Ryzen AI 395+ with 128GB of fast RAM for local AI, or an equivalent Mac Studio. That’s definitely not because I’m “lazy,” it’s because I can’t run a decent model on a raspberry pi
- mrheosuper 1y agoCould you clarify more, AFAIK there is no M1 with 32gb ram machine.
- flkenosad 1y agoM1 Pro
- mrheosuper 1y agoWell it's quite different from the M1. Please don't mix it. It like saying i3 and i7 is the same if they are on the same generation.
- astrange 1y agoIt's not that different. It has more cores but they're the same cores.
- mrheosuper 1y agoAnd higher power limit, exactly like i3 and i5 and i7. Same core architecture, just different in clock, power and core count.
- saagarjha 1y agoI think they have the same microarchitecture but are slightly different (in, like, the number of address bits)
- sudoshred 1y agoMy m1 16gb pro gets throttled (and manually restarted) every time vs code hits 100gb ram usage when running jest unit tests. Don’t know who to blame but 99% sure the problem is my source code and not the machine.
- kjkjadksj 1y ago100gb ram usage? Why not build a pc?
- gigatexal 1y agoChrome eats all my resources too and I have 128GB of ram. Some pages like ClickUp and the Google cloud console (bigquery) eat something like 3-5GB
- raddan 1y agoYou’re chewing through 100GB of RAM on unit tests? What is filling your RAM? Are you sure that you don’t have a memory leak somewhere?
- sudoshred 1y agoI’m certain it’s a memory leak, just not sure solving the problem is worth my time.
- fouc 1y agoyou could try moving your dev environment & docker into a linux VM.. could do something similar to this: https://medium.com/carvago-development/my-docker-on-macos-part-1-setup-ubuntu-virtual-machine-both-intel-and-apple-silicon-cpu-5d886af0ebba https://medium.com/carvago-development/my-docker-on-macos-pa... I mention this because I'm guessing you might be using Desktop Docker which is kinda slow.
- noname120 1y agoOr maybe just switch to OrbStack: https://orbstack.dev/ https://orbstack.dev/
- hombre_fatal 1y agoWon’t change how slow it is to run docker containers in VMs on macOS.
- michelb 1y agoOSX file I/O is really, really slow with large amounts of small files. Wondering if Apple will ever fix that.