![]() Library/StartupItems/MySQLCOM/MySQLCOM start. One word of warning: don’t start/stop/restart MySQL with sudo If the formula is from a keg, cd Library/Taps/KEG.Īpache is installed but not started by default run apachectl -k start toĭo basic admin with sudo apachectl -k ~/Library/LaunchAgents/.On the rare occasion that I’ve needed to, I Older version, but only if you already have it installed. Homebrew is great at upgrading, and you can use brew switch to downgrade to an Here are some packages I’ve installed so far: PATH environment variable for OS X apps with emacsclient, you need to add that path to the default apps to use binaries installed by homebrew in ![]() You can symlink them directly intoĪnother note: for. One note: homebrew formulae that include. A while back I might have usedīut the new hotness now is Homebrew, which Apple’s App Store is nice, but it’s aimed at end users, so it’s not so ![]() Pretty much all the rough edges you might hit on a Linux distro.Įven so, it’s a big change from what I’m used to. Darwin is definitelyĭifferent from Linux, but it’s close enough to feel familiar, and smooths over Is a usable, pretty skin on top of a real POSIX OS. I wasn’t excitedĪbout it, but it’s better than I expected. (Also note that there is some overlap between wired memory and the vmware-vmx resident set, so it's misleading to simply add these numbers.)Īlso, as HPreg said above, the memory usage will grow up to a point (as the VM starts utilizing more of its "physical" memory) but it should not grow in an unbounded way.My current Mac setup instructions are here instead.Īfter 12 years on Linux, I’m grudgingly switching to Mac OS X. In your example above, VMware Fusion was using only about 90MB above the amounts you see vmware-vmx and the UI using. I can't speak for the behaviour of unreleased products, but on the VMware Fusion private beta, your system's wired memory will be roughly equal to the wired memory when no VMs are running plus, for each VM, an amount roughly equal to the working set of that VM. Wired memory is also now completely unavailable to other applications on your system, since Mac OS can't (on its own) swap that memory out to disk. Memory that the VM is actively using is "wired" in order to keep Mac OS from reclaiming it unexpectedly. There are a lot of different ways to measure this, but the most important figure is probably wired memory. Any VM memory that's needed by VMware itself will show up in the vmware-vmx process, but the bulk of memory in a virtual machine ends up being needed only by the guest OS and by the VMM. The VM's memory isn't "allocated" from your host in a fixed block, it is paged in as needed. Things are further complicated by the way VMware manages memory. This doesn't account for shared libraries which may be used only by that process, and it doesn't account for data that the OS is caching on that process's behalf. This is RSS on linux or RSIZE on Mac OS's "top". Typically, on unix-like operating systems, you want to use the number of pages owned by that process that are physically resident in memory. It's very hard to measure the amount of memory actually "used" by a process. That said, it's a little surprising to me that the cached memory would be reclaimed so quickly after stopping the VM. That's not surprising- even if the VM was idle, the process of booting a VM will cause a lot of disk activity, and that disk activity will be cached by Mac OS. Most of this is going to be in the form of cached disk blocks. This means that, while Fusion was running, Mac OS found some way to use nearly all the physical memory on your system. This means Fusion was using over a 1 GB of ram. With Fusion running a VM, my stats are as follows:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |