Using Rhino with a MacBook Air M5

My late-2019 16-inch Intel MacBook Pro (i9, 32 GB RAM, 1 TB SSD) died this week, so I am now currently looking for a replacement.

Replacing it with a MacBook Air is my current preference. My MBP was top spec in 2020 and performed well enough but I always found it bulky and cumbersome. Also I now have a PC desktop workhouse which handles rendering and other more demanding tasks.

Given current spikes in computer hardware prices I was hoping to go with the base configuration 16GB RAM and 512GB SSD for the Air but I’ve heard mixed reports about whether 16GB of RAM is sufficient. Just to put it in context bumping the RAM from 16GB to 24GB is +€225 and to 32GB is +€450 which just seems insane to me.

I would appreciate feedback from anyone using the MacBook Air with Rhino (and architectural work more broadly) what their experiences have been like. Did you notice the computer reaching its limits and lagging and if so when? There is nothing worse than a stuttering lagging interface when you’re trying to model.

Just for reference, my typical files consist of detailed residential project proposals ranging from 200 MB to 400 MB (rarely exceeding 500 MB). I do not model large-scale urban masterplans or massive site topographies on this machine. I do not currently use Grasshopper, which I understand is where RAM usage increases significantly but I keep telling myself to start using it so perhaps I should account for that also. I was thinking about getting Enscape for Mac also so I can utilise real time rendering.

I would really appreciate hearing about your personal experiences using this system so I don’t buy the wrong machine and end up regretting it.

i always used this rule of thumb:

do not buy …
… the minimum configuration … it will be outdated to fast
… the maximum configuration … apple get s to expensive on this.

buy the maximum in between you can afford.

:cold_face:

if you post some file, people can tell you how it feels on their machines and how much memory is consumed by rhino while it is open.

are you doing renderings ?

I can’t speak for the newer models, but I have been rocking Rhino on an M2 Air with a measly 8Gb of RAM for the past couple of years. It’s sufficient for my needs - mostly making parts for the CNC machine and printer. I did also make a floor plan and model of our factory. Simple Grasshopper scripts run fine, though I’m still a novice when it comes to Grasshopper

If the file size is under 100Mb it doesn’t seem to struggle. Over that, and it begins to sweat. Ray tracing take minutes, hardly ideal when the desktop took seconds, so I largely don’t bother with renders

Tom’s advice is sound. Don’t get the base model. 16Gb of RAM would certainly be a boost for my use case, but if you can stomach it, I’d wager that getting more will be sensible if you’re opening files as big as 400 or even 500Mb

Well I guess I can afford more RAM but +USD550 for an extra 16MB RAM kind of seemed extortionist to me. I guess my timing isn’t great with the market being the way it is. I did see some deals on M4 Airs with 32GB that amounted to +USD200. Do you think that would be a better compromise? Dropping back a generation with the processor to bump the RAM by 16GB. It’s not so clearly to me if that will make the system more future proofed or it’s just robbing Peter to pay Paul.

Regarding the rendering most rendering software I use isn’t available on Mac unfortunately. Enscape is my renderer of choice and they now have a Mac version which wasn’t available on the Intel Mac (Apple silicone only) so I never had the chance to use it. It would be nice if that worked on my Air to save me going back and forth on computers but I would only use it to explore the model and not to generate demanding renders.

Linked below are 2 models showing 1. A typical file and 2. A heavy file that I might work on at any given time. If you can open them on a MacBook Air and see how they perform I would be most grateful.

Model.1 (250MB)

Model.2 (530GB)

this is how my memory usage looks, just on this afternoon - closed rhino - when i open your file once and twice in Rhino Beta.

Running System, Spotify, a few browser windows, mail…

Make2d took 62 seconds
and Rhino somehow needs more memory afterwards …

and with this rhino s memory-usage is up to
7.7 GB claimed by rhino
8.8 GB by “Memory” in Activity Monitor
7.5 GB “real Memory” by Activity Monitor

… my guess - you will not be happy with 16 GB setting at all.

Ohhh my, this is the smaller file also. I frequently work on files that size and typically in rendered display mode. Is the file navigation ok or does it stutter? I’d be very interested in seeing how the large file performs. My old 2019 MBP opened and navigated that exact file pretty well.

Also Tom thank you for helping me with this! It is greatly appreciated. You didn’t mention what system you are on. Is it MacBook Air M5 16GB RAM?

navigation on shaded display mode is fluent.
macbook pro, Apple m5 pro, 48 gb, mac os x 27.0.1

Ohhh haha. I’m not sure how much I can glean from that. I suppose the RAM usage is something. You are on a much more powerful machine. I would expect that file would be smooth as butter.

I’m using an 15inch M4 MacBook Air w/ 16GB RAM. I was able to download your 250MB file and it opened quickly. Panning and zooming was fast with no noticeable delays. I switched from shaded to arctic to see how quickly the new views were rendered and it was without noticeable delay.
My Activity Monitor showed only minimal Rhino usage.

Note: I only use Rhino for product design so I’m not as familiar with how it’s used in architecture. If there’s an action you’d like me to perform let me know.

Also, I tried downloading the 500mb file but was denied access to the Google Drive.

Hi Joel thanks a lot! Your system is essentially exactly the one I’m looking to buy so your feedback is super helpful!

I just realised the large file had access permissions turned off. It should work now.

I’m curious to know if navigating the model in rendered view mode is smooth. No stutters or lags.

I was able to download the 530MB file. Panning and zooming in rendered view was fluid and without delay. It felt the same as my much smaller product models.
My activity monitor shows Rhino 8 using 3 GB of memory. I did close and restart my computer before testing your file. I hadn’t restarted my computer in months so this is a clean restart test. The only other program I had started was Safari.

Ok that’s very interesting in light of Tom’s feedback. I wonder why your Air seems to be handling the files better than his MBP. Are you using you air for architectural work? I would be curious to know if you had tested its limits. What tasks and software were you running?

Like I said above, I do product design, mostly furniture and decor items. I’m not a power user but some of my models are complex with many parts. Like you, I upgraded from a MBP Intel-based laptop that was more than adequate for my work. In your case, I would have no problem recommending the M5. I’m sure you’ll be happy compared to your old MBP Intel-based laptop.

15" M5 Air 32 GB

in shaded, 530 MB model gets about 59 f/s, & about 3 f/s in render mode

I did a screen recording of flying around the model, but they r +22 MB, so won’t upload.

but M5 air is def capable, I’ve been using it for rhino for a while.

I learned something new from @yelenaye . Using command “TestMaxSpeed” while in shaded and rendered views, I have the following results:

Shaded: Time to regen viewport 100 times = 1.78 seconds. (56.27 FPS)
Rendered: Time to regen viewport 100 times = 6.81 seconds. (14.68 FPS)

Thanks for this Yelen! Am I right in saying that 3 f/s in rendered view mode is quite a compromised interface? It’s not fluid to pan zoom and orbit around the model?

It’s very interesting that Joel is getting a better frame rate with less RAM (16GB).

you can orbit, but it’s choppy…

wonder which model? 250 or 530

I’m looking at the 530MB model as well. And my MacBook Air is M4, 16GB.

Try using the “TestMaxSpeed” command to see your results.

rgt, that’s how I tested the 530 model. 59 & 3 f/s … interesting!