<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Cloud Sizing for AWS, Azure and Google - What are best instance types to use? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143674#M35624</link>
    <description>&lt;P style="margin-left: 40px;"&gt;  &lt;A rel="user" href="https://community.cloudera.com/users/9304/tspann.html" nodeid="9304"&gt;@Timothy Spann&lt;/A&gt;  "best" is a subjective term when it comes to public cloud providers.  I would take your typically on perm profile and back port it to the AWS EC2 profiles. From a pricing perspective you can further spread the master/datanodes services to small boxes based on cost difference.  For example ZK uses low ram.  Then you can find a small 2-4gig box for your ZK quorum.  Take the typical on perm requirements and back port into 1:M VM on your cloud provider.  &lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;For example &lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Master Nodes - Multipule of m4.4xlarge, or r3.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Data nodes - i2.4xlarge or d2.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Storm nodes - c4.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Spark - x1.32xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;GPU processing - g2.2xlarge&lt;/P&gt;</description>
    <pubDate>Fri, 22 Jul 2016 21:32:08 GMT</pubDate>
    <dc:creator>sunile_manjee</dc:creator>
    <dc:date>2016-07-22T21:32:08Z</dc:date>
    <item>
      <title>Cloud Sizing for AWS, Azure and Google - What are best instance types to use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143673#M35623</link>
      <description>&lt;P&gt;What are the best instance types for HDP nodes (master, data, edge)?&lt;/P&gt;&lt;P&gt;I found a number of instance types that may work. &lt;/P&gt;&lt;P&gt;Looking at&lt;/P&gt;&lt;P&gt;TCO&lt;/P&gt;&lt;P&gt;&lt;A href="https://awstcocalculator.com/" target="_blank"&gt;https://awstcocalculator.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Rough Pricing&lt;/P&gt;&lt;P&gt;&lt;A href="https://calculator.s3.amazonaws.com/index.html" target="_blank"&gt;https://calculator.s3.amazonaws.com/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Amazon Types&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.ec2instances.info/" target="_blank"&gt;http://www.ec2instances.info/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Amazon EC2 Types&lt;/P&gt;&lt;P&gt;&lt;A href="https://aws.amazon.com/ec2/instance-types/" target="_blank"&gt;https://aws.amazon.com/ec2/instance-types/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 10:31:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143673#M35623</guid>
      <dc:creator>TimothySpann</dc:creator>
      <dc:date>2022-09-16T10:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Sizing for AWS, Azure and Google - What are best instance types to use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143674#M35624</link>
      <description>&lt;P style="margin-left: 40px;"&gt;  &lt;A rel="user" href="https://community.cloudera.com/users/9304/tspann.html" nodeid="9304"&gt;@Timothy Spann&lt;/A&gt;  "best" is a subjective term when it comes to public cloud providers.  I would take your typically on perm profile and back port it to the AWS EC2 profiles. From a pricing perspective you can further spread the master/datanodes services to small boxes based on cost difference.  For example ZK uses low ram.  Then you can find a small 2-4gig box for your ZK quorum.  Take the typical on perm requirements and back port into 1:M VM on your cloud provider.  &lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;For example &lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Master Nodes - Multipule of m4.4xlarge, or r3.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Data nodes - i2.4xlarge or d2.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Storm nodes - c4.4xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;Spark - x1.32xlarge&lt;/P&gt;&lt;P style="margin-left: 40px;"&gt;GPU processing - g2.2xlarge&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2016 21:32:08 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143674#M35624</guid>
      <dc:creator>sunile_manjee</dc:creator>
      <dc:date>2016-07-22T21:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Cloud Sizing for AWS, Azure and Google - What are best instance types to use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143675#M35625</link>
      <description>&lt;P&gt;Thanks for the analysis.   Does anyone have similiar sizings for Google and Azure:&lt;/P&gt;</description>
      <pubDate>Sat, 23 Jul 2016 04:17:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloud-Sizing-for-AWS-Azure-and-Google-What-are-best-instance/m-p/143675#M35625</guid>
      <dc:creator>TimothySpann</dc:creator>
      <dc:date>2016-07-23T04:17:51Z</dc:date>
    </item>
  </channel>
</rss>

