RhinoCompute system requirements for cloud VM

Hi there,

We’re in the early stages of building something that will see us use RhinoCompute in Azure (running in a Windows Server 2016 VM as per repo requirements) and ran into a question : our client’s Azure solutions architect is asking for system requirements for running this VM ? We’ll probably need at least 2 in a HA cluster for when we go to production, so having the right/wrong specs can have quite a big financial impact.

Obviously, there are documented requirements for Rhino 6 itself, but none for running RhinoCompute. Since it’s running headless, I assume the OpenGL 4.1 graphics card requirement is moot, but even the 8GB RAM will be hard/costly to achieve in a VM environment, so wondering what the minimum is.

I realise the docs reference AWS and not Azure, but any guidance on these system requirements will be very useful - even if AWS instance size, specs etc.


cc @will

Hey @radug! System requirements are not concrete at this point – we’re still in the learning stage. I can however share with your our experience so far. Currently, for compute.rhino3d.com, we’re running a cluster of four t2.medium instances (general purpose, 2 vCPU, 4 GB RAM) behind a load balancer and it seems to be behaving well. Of course, if you’re going to be sending large meshes back and forth and running heavy boolean computations then you’ll need higher specs!


Awesome, thanks for the lightning-fast response @will !

If you’re allowed to share this info : any indication what kind of usage numbers the 4 instances cover ?
(reqs/day for example)

Found this basic mapping table between AWS & Azure instances for anyone else needing it.

You’re welcome! Most activity in the last month was 6k successful POST requests over three hours.

1 Like

Sorry, I was mistaken. We’re using t2.medium instances, not t2.small. :lying_face:

I’ve edited my post above!

1 Like

Thanks @will :clap: