For production purposes this is doable considering I would probably end up scaling to these specifications anyway, but for my secondary development environment this is quite a pricy setup. Then there is the issue of cost, in my case I required the NV-Series which meant the smallest possible VM size is 6 vCPUs with 56GB of RAM, coming in at just over 1000 EURO a month.
STARBOUND OPENGL 2.0 NOT FOUND SERIES
You can find the availability of these, and other series here. Region availability is another issue for this newer VM series, as with other specialized compute products, availability is not as widely supported as the, lets say ‘bread and butter’ VMs. So, we will have to do with Standard HDD or Standard SSD storage. There are still some drawbacks to using these Virtual Machines, primarily the fact that at the time of writing they don’t support Premium (SSD) storage or Premium Storage Caching. Each subseries offers different CPU and GPU combinations for different computing scenarios.
The N-Series are divided into several subseries, for instance the NC, NC, ND, NCS and NVC-Series. Azure’s N-Series Virtual Machines are the first Azure Virtual Machines that come with NVIDIA Tesla GPU’s and with that provide support for DirectX and OpenGL. Luckily Azure has expanded their VM range to now also include special VM series that are optimized for graphical processing. The classic ‘but it worked on my PC’-line soon followed. I recently ran into this issue when publishing my 3D modelling application that uses ParaView for image rendering from my local development environment to my Azure VM. Azure Virtual Machines by default don’t come with GPU capabilities, making them mostly useless for processes that require a GPU in anyway.
0 kommentar(er)
