Published On: Wed, Feb 17th, 2016

Google’s Custom Machine Types Come Out Of Beta, Now Support Red Hat And Windows

Custom Machine Types on Google’s Cloud Platform concede we to select accurately how many CPU cores and how most memory we wish in a practical appurtenance to run your applications. Google initial introduced this underline final Nov and currently it is holding it out of beta.

In addition, Google currently introduced support for using both Red Hat’s Linux placement and Windows on these machines. That’s on tip of Google’s existent support for CentOS, CoreOS, Debian, OpenSUSE and Ubuntu. If we need a tradition setup, we can always move your possess Linux placement to a service, too.

With today’s update, both Google’s Container Engine and Deployment Manager now benefit support for Custom Machine Types, too.

Screen Shot 2015-11-18 during 9.09.00 AM

The advantage of Custom Machine Types is that we compensate a prosaic price per practical CPU core ($0.03492 per core per hour in a U.S.) and GB of memory ($0.00468 per GB per hour). If, for some reason, we need 3 cores and 15 GB of memory, we can now select this multiple instead of stepping adult to a pre-set — and some-more dear — appurtenance form that would close we into 4 cores and 20 GB of memory.


Google says a business are saving an normal of 19 percent (and adult to 50 percent) after switching to tradition appurtenance types, though this apparently always depends on a particular use case. The association says Wix, for example, cut a discriminate cost for powering a media height by 18 percent and selling personalization use Lytics saved between 20 and 50 percent.

Pricing for these appurtenance forms follows Google’s customary indication and includes support for per-minute billing and postulated use discounts.

About the Author

Leave a comment

XHTML: You can use these html tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>