Live data from Hacker News

How fast is a macOS VM, and how small could it be?

eclecticlight.co

91–100 of 111 posts

Re: How fast is a macOS VM, and how small could it be?

#91
post #72

Earlier quoted context omitted.

Try Apple's container CLI. I moved a project of mine from colima+docker to it relatively easily, a couple of weekends ago. https://github.com/apple/container

Does this project aim for docker cli and api compatibility? Searching for Docker on that page yields no results. Though in their example, they do show an example of a Dockerfile referencing docker.io without shame. Typical Apple behavior, I guess, but grating to see in a OSS tool.

This is a weird take, imho. Should they feel shame for using Dockerfiles in their OCI-standard-compliant tool? Would you be happier if they introduced subtly incompatible Applefiles?

Why are they obliged to emulate the Docker CLI? This limits them to just shadowing someone else's product. Just use Docker if you want their CLI/API, it uses the same virtualization framework under the hood on Macs.

Re: How fast is a macOS VM, and how small could it be?

#92

Honestly macOS probably can go much lower than that if you turn off some stuff that's not strictly necessary for a VM. The first iPhones only had 128 MiB of RAM and they ran a trimmed down version of macOS Tiger I believe. It's just that RAM has been quite abundant so far, so there was no real reason to try to trim it down, but it's definitely possible, and probably not that hard either, we just need to start trying…

Maybe I’m nitpicking but there is no such thing as “macOS Tiger”. It’s called Mac OS X at the time so it’s Mac OS X Tiger.

Re: How fast is a macOS VM, and how small could it be?

#95
post #7

>Starting with 4 virtual cores and 8 GB vRAM, where the VM ran perfectly briskly with around 5 GB of memory used, I stepped down to 3 cores and 6 GB, to discover that memory usage fell to 3.9 GB and everything worked well. With just 2 cores and 4 GB of memory only 3.1 GB of that was used, and the VM continued to handle those lightweight tasks normally. Good reminder that there's a certain amount of memory tied up wit…

As a general rule, also the amount of physical memory installed in a computer should be proportional with the number of hardware threads provided by its CPU. Besides the fact that the operating system may allocate some memory for each thread, when you launch a multi-threaded application that is able to use all available threads, for instance the compilation of a big software project, it frequently will allocate some…

[deleted]

Re: How fast is a macOS VM, and how small could it be?

#98
post #75
post #70

Earlier quoted context omitted.

My experience along with thousands others (incl 100 other Macs at work) is that of stability. You're saying the opposite based on some Reddit threads. Not sure what your intentions are. Yes, modern OS's might have issues in runtime, but of the top 3, I am pretty sure macOS is the most stable. Linux wins on the server side though.

I'm happy for your personal experience; it clearly doesn't jive with the numerous threads on the macos reddit forum for first and third party apps causing OOM issues (which macOS ungracefully handles, unlike NT). > Not sure what your intentions are. This is just a weird statement. > Yes, modern OS's might have issues in runtime /All/ modern general purpose OSes have issues at runtime. Every last one of them. macOS is…

Looking at your comment history - it does seem you have an agenda. I don't get it. Yet your references are mostly anecdotes from random forums that back your claim. You'll find that for any OS or any piece of software if you go looking.

Re: How fast is a macOS VM, and how small could it be?

#99
post #13

Earlier quoted context omitted.

> the signing/notarization just ~200 lines of Bash 200 lines?! That’s two orders of magnitude too many. What exactly are you doing that you need so such code for signing and notarisation?

From the top of my head, unlocking the keychain, finding the right identity, notarizing two parts, the binary itself and the .dmg that the .app ships in and some other stuff I'm sure. Can do a deeper look in a bit when I can. Most of the hassle is because it's 100% unattended and I had to do stuff to avoid GUI-prompts for passwords/unlocks, and that the Forgejo Runner has a different security context.

> unlocking the keychain, finding the right identity

You don’t need to do that, you can give options to the CLI to define what profile to use.

> Most of the hassle is because it's 100% unattended and I had to do stuff to avoid GUI-prompts for passwords/unlocks

I have a shell function to which I point my code and it compiles, signs, and notarises it without any more intervention, GUI or password prompts, and I’m pretty sure signing and notarising are literally two lines.

Unfortunately I’m not at my computer now or I’d paste them, but from your description that script is definitely too long.

Re: How fast is a macOS VM, and how small could it be?

#100
post #99

Earlier quoted context omitted.

From the top of my head, unlocking the keychain, finding the right identity, notarizing two parts, the binary itself and the .dmg that the .app ships in and some other stuff I'm sure. Can do a deeper look in a bit when I can. Most of the hassle is because it's 100% unattended and I had to do stuff to avoid GUI-prompts for passwords/unlocks, and that the Forgejo Runner has a different security context.

> unlocking the keychain, finding the right identity You don’t need to do that, you can give options to the CLI to define what profile to use. > Most of the hassle is because it's 100% unattended and I had to do stuff to avoid GUI-prompts for passwords/unlocks I have a shell function to which I point my code and it compiles, signs, and notarises it without any more intervention, GUI or password prompts, and I’m prett…

I assume you're using notarytool but I doubt that it will work unless you have your keychain unlocked
Post reply on HN