{"id":58586,"date":"2020-02-11T13:00:00","date_gmt":"2020-02-11T19:00:00","guid":{"rendered":"https:\/\/eshop.macsales.com\/blog\/?p=58586"},"modified":"2020-09-15T16:51:11","modified_gmt":"2020-09-15T21:51:11","slug":"6000-tabs-of-google-chrome-vs-1-5tb-of-owc-memory-who-will-win","status":"publish","type":"post","link":"https:\/\/eshop.macsales.com\/blog\/58586-6000-tabs-of-google-chrome-vs-1-5tb-of-owc-memory-who-will-win\/","title":{"rendered":"6,000 Tabs of Google Chrome vs. 1.5TB of OWC Memory. Who Will Win?"},"content":{"rendered":"\n
\"1.5TB<\/a>
This is what 1.5TB of OWC Mac Pro memory looks like<\/figcaption><\/figure><\/div>\n\n\n\n

The Question<\/h2>\n\n\n\n

We had a simple question:
\u2022 What would happen if we pushed a top of the line, 28-core Mac Pro loaded with 1.5TB of OWC memory, to its limits? <\/em><\/p>\n\n\n\n

Which begged a second question:
\u2022 What exactly is the best way to do that?<\/em><\/p>\n\n\n\n

This latter inquiry was easy enough to answer. We just needed to reach out to our friend, Jonathan Morrison. He would know how to get to the bottom of this.<\/p>\n\n\n\n

For the uninitiated, Jonathon is a beast of a Tech Reviewer with over 2.6 million followers on his TLD YouTube channel<\/a>. He focuses primarily on Apple products, and we knew he would come up with the perfect testing solution for our RAM. What he devised was elegantly simple:<\/p>\n\n\n\n

  1. Install 1.5TB of OWC memory<\/a> in a 2019 28-core Mac Pro<\/li>
  2. Launch Google Chrome<\/li>
  3. Open as many tabs with real websites as possible<\/li>
  4. See what happens<\/li><\/ol>\n\n\n\n

    Why Chrome? Because it is easily automated and can be quite the memory hog. And why is it such a memory hog? The answer to that question is a lengthy post for another day. But if you are interested in a quick synopsis, check out Lifehacker’s article, Why Chrome Uses So Much Freaking RAM<\/em><\/a>.<\/p>\n\n\n\n

    \"Jonathan<\/a>
    Jonathan Morris Installing 1.5TB of OWC memory into a Mac Pro.<\/figcaption><\/figure><\/div>\n\n\n\n
    \n\n\n\n

    The Answer<\/h2>\n\n\n\n

    Spoiler Alert:<\/strong> The memory didn\u2019t fail, nor was its performance any sort of bottleneck. Using up nearly every byte of available RAM with over 6,000 tabs open 😲, Chrome just decided it had had enough, and stopped trying. Our 1.5TB of memory can certainly eat a lot of Chrome.<\/p>\n\n\n\n

    So, enjoy the video below, subscribe to Jonathan\u2019s YouTube<\/a> channel, follow him on Twitter<\/a>, Facebook<\/a>, and Instagram<\/a>, and most importantly, buy some OWC memory<\/a> and save yourself up to 65% over Apple\u2019s factory installed options!<\/p>\n\n\n\n

    \n\n\n\n

    The Video<\/h2>\n\n\n\n
    \n