你最喜欢的网络浏览器(web browser)是什么？您是否(Are)有机会使用Google Chrome 浏览器(Google Chrome)？您使用 Chrome 64 位还是 Chrome 32 位？如果您仍在使用 32 位版本，但您的Windows是 64 位，您也应该考虑切换到 64 位Google Chrome。您想知道哪个是最好的、最快的还是系统要求较低(lesser system)的？我们也问过自己所有这些问题，所以我们决定回答这些问题。我们运行了几个基准测试，我们测量了RAM 消耗(RAM consumption)，我们在网上搜索了信息，我们最终得到了这篇文章。如果您想知道 64 位和 32 位版本的区别谷歌浏览器(Google Chrome)，继续阅读：
Google Chrome 64 位与 32 位 - 基准测试中的性能
我们首先在几个基准测试工具中测试了两个版本的Google网络(Google)浏览器： (web browser)HTML5 测试(HTML5 test)、JetStream 1.1、Peacekeeper、Basemark Web 3.0、Octane 2.0和MotionMark 1.0。除HTML5 测试(HTML5 test)外，每个基准测试都运行了 3 次，我们记录了平均分数。我们用于测试的机器是一台按当今标准平均性能的中端计算机：运行频率为 4.0 GHz的(GHz)AMD FX8350 处理器(AMD FX8350 processor)、频率为 2133MHz 的8GB DDR3和2GB 的AMD Radeon R9 270X显卡(video card) GDDR5 内存(GDDR5 memory)。我们将Windows 10 Professional 版本 1703(Professional version 1703)与 Creators Update一起使用。
HTML5 测试(HTML5 test)分数表明您的浏览器对HTML5标准(HTML5 standard)及其相关规范的支持程度。从下图中可以看出，64 位版本的Google Chrome对(Google Chrome)HTML5 标准(HTML5 standard)的支持水平与 32 位版本相同。这是意料之中的，因为我们正在比较同一浏览器的不同版本。
JetStream 1.1基准测试运行延迟测试，以测量 Web 应用程序启动和提升到峰值性能的速度，以及无中断平稳运行的速度。它还运行吞吐量测试来衡量 Web 应用程序的持续峰值性能。最高的结果意味着更快的速度和更好的性能。正如您在下面的屏幕截图中看到的，我们得到的结果并没有那么不同。但是，64 位版本的Google Chrome比 32 位版本快 8%。
接下来，我们使用了Peacekeeper 基准(Peacekeeper benchmark)，这是一个较旧的基准，但它今天仍然与网络(web today)相关。Peacekeeper通过测试浏览器的JavaScript 渲染(JavaScript rendering)和处理常用JavaScript函数的能力来衡量浏览器的性能。64 位版本的谷歌浏览器(Google Chrome)再次成为赢家，得分相差 4%。
我们使用的下一个测试是Basemark Web 3.0。它测量以 2D 和 3D 呈现对象以及一次处理多个CSS操作的能力。它还说明了浏览器对CSS3、HTML5、Flash 和 Silverlight(Flash and Silverlight)的支持程度，以及浏览器加载页面和发送请求的速度。在本次测试中，64 位版本的谷歌浏览器(Google Chrome)再次以近 6% 的优势获胜。
Octane 2.0是由Google自己开发和维护的基准。(benchmark developed)此基准测试衡量您的网络浏览器的(web browser)JavaScript 性能(JavaScript performance)，并运行一系列测试，涵盖网络上最常见的用例。64 位版本的Google Chrome获得的结果比 32 位版本的结果要好近 7%。
最后，我们还运行了MotionMark，这是一个专注于图形性能的基准测试。它运行的测试在视觉上很丰富，旨在强调图形系统而不是JavaScript。Google Chrome 64 位(Google Chrome 64-bit)的性能比其 32 位版本高 16%。
Google Chrome 64 位与 32 位 - RAM 消耗(RAM consumption)
RAM 内存消耗与(RAM memory)JavaScript 或图形性能(JavaScript or graphics performance)一样重要，尤其是当您使用速度较慢的设备时，RAM比平均水平要少。要查看Google Chrome(Google Chrome)的 64 位和 32 位版本需要多少RAM 内存，我们执行了以下操作：(RAM memory)
- 我们使用了以当今标准计算的平均性能的中端计算机：运行频率为 4.0 GHz的(GHz)AMD FX8350 处理器(AMD FX8350 processor)、频率为 2133MHz 的8GB DDR3和具有 2GB GDDR5 内存的(GDDR5 memory)AMD Radeon R9 270X显卡(video card)，所有这些都在Windows 10专业版上运行(Professional version 1703)1703与创作者更新(Update)。
- 我们安装了Google Chrome 64 位(Google Chrome 64-bit)，然后安装了 Google Chrome 32 位(Google Chrome 32-bit)，并且对于它们中的每一个，我们都打开了相同的选项卡。我们试图复制一个真实的场景(real-life scenario)，所以我们为这些网站中的每一个打开了标签：Gmail、Facebook、CNN、YouTube、BoredPanda和Digital Citizen - 为我们提供了 2 个标签。🙂
- 对于我们打开的每个网站，我们都会尽可能多地滚动它们的内容。这意味着Facebook必须继续将内容加载到其新闻提要(news feed)中，直到它不再显示任何内容，并以“如果您添加更多朋友，您将在新闻提要中获得更多故事”的有趣消息停止。("You'll have more stories in News Feed if you add more friends.")在YouTube的情况下，我们不仅加载它，而且还在其中播放了一个视频。
在我们看来，我们希望你也一样，以上所有内容都应该使情况尽可能接近现实。为了检查Google Chrome(Google Chrome)使用了多少RAM 内存(RAM memory)，我们使用了它的任务管理器(Task Manager)功能。这是因为它显示了有关在Google Chrome(Google Chrome)中打开的每个选项卡的详细信息，而不是您在 Windows中的任务管理器中获得的信息。(Task Manager)
当我们使用 64 位版本时，谷歌浏览器(Google Chrome)消耗了高达 1.19 GB 的RAM 内存(RAM memory)来加载我们上面列举的所有选项卡。
当我们使用它的 32 位版本时，谷歌浏览器(Google Chrome)只需要 634 MB 的RAM 内存(RAM memory)来加载所有这些选项卡。
如您所见，在现实生活中，64 位版本的Google Chrome需要的(Google Chrome)RAM 内存(RAM memory)几乎是 32 位版本所需的两倍。不幸的是，这对于使用低端设备的人来说不是好消息，没有足够的RAM 内存(RAM memory)。
Google Chrome 64 位与 32 位在速度、安全性和稳定性(security & stability)方面需要考虑的其他事项
当谷歌在 2014 年宣布推出(Google announced the launch)64 位版本的Chrome时，他们还分享了一些关于用户应该期待什么的信息。除了我们在基准测试中测得的稍快的性能外，还有一些使用此类测试工具无法衡量的优势：
- 处理图形和视频时(Improved speed when dealing with graphics and video)提高了速度- 64 位版本的Google Chrome提高了图形和视频的速度，包括高清 YouTube 视频(High Definition YouTube videos)。例如，在高清 YouTube 视频(High Definition YouTube videos)中使用的VP9 编解码器(VP9 codec)显示解码性能提高了 15 % improvement结果，速度提高了，性能提高了 25%，尤其是在图形和多媒体内容(multimedia content)方面。
- 更好(Better security)的安全性 - 64 位版本的Google Chrome可以利用Windows 8.1和Windows 10中包含的新安全功能。例如，它增加了对高熵 ASLR(High Entropy ASLR)（地址空间布局随机化(Space Layout Randomization)）的支持，它提供了额外的保护层(protection layer)和更好地防御利用技术。ASLR基于攻击者猜测随机放置区域位置的可能性很小。通过增加搜索空间来增加(search space)安全(Security)性。因此，地址空间随机化(space randomization)当随机偏移中存在更多熵（无序）时，效率更高。这可以防止攻击者可靠地跳转到内存中的特定被利用函数。额外的位迫使软件使用所有资源来获得最大的防御，改进现有的安全功能。
- 提高了稳定性(Improved stability)——在处理Web 内容时， (web content)64 位渲染(64-bit rendering)引擎的稳定性几乎是 32 位引擎的两倍。特别是渲染过程的(rendering process)崩溃率(crash rate)比 32 位版本的谷歌浏览器(Google Chrome)小近 50% 。
后来，在 2016 年底，谷歌(Google)发布了另一篇博客文章(blog post)，其中他们宣布 64 位Chrome已开始使用微软(Microsoft)的配置文件引导优化( Profile Guided Optimization)( PGO ) 技术，这使得Chrome在(Chrome)Windows上的速度提高了 15% ，截至版本53(version 53) . 但是，如果您使用 32 位，您将获得相同的提升，但仅限于54(version 54)或更高版本。
结论(Conclusion)-谷歌浏览器 64 位(Google Chrome 64-bit)值得使用
可以肯定地说，在使用 64 位版本的谷歌浏览器(Google Chrome)时，大多数用户的网页浏览体验不会有任何差异。在性能方面，我们的测试表明存在差异。但是，它们可能仍然太小而无法在日常使用中感觉到。另一方面，还需要考虑RAM 内存(RAM memory) 消耗因素(consumption factor)。由于 64 位Google Chrome所消耗的内存大约是 32 位版本的两倍，因此对于使用低端设备的人来说，这可能是一颗难以下咽的药丸。但是，最后，我们认为稳定性和安全性(stability and security)提高等额外好处使这次升级值得(upgrade worthwhile). 如果您观看大量高清视频或在网络浏览器(web browser)中玩游戏，则尤其如此。如果您今天想切换到 64 位版本的Google Chrome(Google Chrome today)，请转到此页面(page)并从那里下载。
Google Chrome 64-bit: Is it better than the 32-bit version?
What'ѕ your favorite web browser? Are you, by any chance, υsing Gоogle Chrome? Do you use Chrome 64-bit оr Chrome 32-bit? If you are still using the 32-bit version but your Windows is 64-bit, you should consider switching to the 64-bit Google Chrome as well. Do you wonder which іs best, or the fastest, or the оne with the lesser system requirеments? We asked ourselvеs all that too, so we decided to gеt an anѕwer to these questions. We ran several benchmarks, we measured RΑM consumption, we scoured the web for infоrmation, and we ended up with this article. If you want to know what's different between the 64-bit and 32-bit versions of Google Chrome, read on:
Google Chrome 64-bit vs. 32-bit - Performance in benchmarks
We started by testing the two versions of Google's web browser in several benchmarking tools: HTML5 test, JetStream 1.1, Peacekeeper, Basemark Web 3.0, Octane 2.0, and MotionMark 1.0. Each benchmark except the HTML5 test was run three times, and we recorded the average score. The machine we used for testing is a mid-range computer with average performance by today's standards: AMD FX8350 processor running at 4.0 GHz, 8GB of DDR3 at 2133MHz, and an AMD Radeon R9 270X video card with 2GB of GDDR5 memory. We used Windows 10 Professional version 1703 with Creators Update.
The HTML5 test score is an indication of how well your browser supports the HTML5 standard and its related specifications. As you can see from the following graph, the 64-bit version of Google Chrome offers the same level of support for the HTML5 standard as the 32-bit version. This is to be expected since we are comparing different versions of the same browser.
The JetStream 1.1 benchmark runs latency tests which measure how quickly web applications can start and ramp up to peak performance, and run smoothly without interruptions. It also runs throughput tests which measure the sustained peak performance of web applications. The highest results mean faster speed and better performance. As you can see in the screenshot below, the results we got are not that different. However, the 64-bit version of Google Chrome was 8% faster than the 32-bit version.
Next, we used the Peacekeeper benchmark which is an older benchmark, but it is still relevant to the web today. Peacekeeper measures the browser's performance by testing its JavaScript rendering and its ability to handle commonly used JavaScript functions. The 64-bit version of Google Chrome was the winner again, with a difference between scores of 4%.
The next test we used was Basemark Web 3.0. It measures the ability to render objects in 2D and 3D and crunch multiple CSS operations at a time. It also tells how well the browser supports CSS3, HTML5, Flash and Silverlight and how fast the browser loads pages and send requests. In this test, the 64-bit version of Google Chrome was again the winner, with a margin of almost 6%.
Octane 2.0 is a benchmark developed and maintained by Google themselves. This benchmark measures the JavaScript performance of your web browser, and it runs a series of tests which cover the most common use cases found on the web. The 64-bit version of Google Chrome managed to get a result that's better by almost 7% than what the 32-bit version achieved.
Finally, we also ran MotionMark, a benchmark that focuses on graphics performance. The tests it runs are visually rich, and designed to stress the graphics system rather than JavaScript. Google Chrome 64-bit had a performance that was 16% better than its 32-bit version.
Google Chrome 64-bit vs. 32-bit - RAM consumption
RAM memory consumption is just as important as JavaScript or graphics performance, especially if you are using a slower device, with less RAM than average. To see how much RAM memory is needed by Google Chrome's 64-bit and 32-bit versions, we did the following:
- We used a middle-range computer with an average performance by today's standards: AMD FX8350 processor running at 4.0 GHz, 8GB of DDR3 at 2133MHz, and an AMD Radeon R9 270X video card with 2GB of GDDR5 memory, all running on Windows 10 Professional version 1703 with Creators Update.
- We installed Google Chrome 64-bit and then Google Chrome 32-bit, and for each of them, we opened the same tabs. We tried to copy a real-life scenario, so we opened tabs for each of these websites: Gmail, Facebook, CNN, YouTube, BoredPanda, and Digital Citizen - 2 tabs for us. 🙂
- For each website that we opened, we scrolled their contents as much as it was possible. That meant that Facebook had to keep on loading content into its news feed until it had nothing to show anymore, and stopped with a funny message of "You'll have more stories in News Feed if you add more friends." In the case of YouTube, we did not just load it, but we also played a video in it.
In our opinion and we hope that in yours too, all of the above should make for a situation as close to reality as possible. To check how much RAM memory is used by Google Chrome, we used its Task Manager feature. That is because it shows more detailed information about each tab opened in Google Chrome than the information you get in the Task Manager found in Windows.
When we used the 64-bit version, Google Chrome ate a whopping 1.19 GB of RAM memory to load all the tabs we enumerated above.
When we used its 32-bit version, Google Chrome needed only 634 MB of RAM memory to load all those tabs.
As you can see, in real life situations, the 64-bit version of Google Chrome needs almost twice the RAM memory required by the 32-bit version. Unfortunately, that is not good news for people who use low-end devices, with not enough RAM memory.
Other things to consider about Google Chrome 64-bit vs. 32-bit regarding speed, security & stability
When Google announced the launch of the 64-bit version of Chrome, in 2014, they also shared some information about what users should expect from it. Besides the slightly faster performance we have measured in benchmarks, there are also advantages that cannot be measured with such testing tools:
- Improved speed when dealing with graphics and video - the 64-bit version of Google Chrome improves the speed of graphics and video including High Definition YouTube videos. For example, the VP9 codec used in High Definition YouTube videos shows a 15% improvement in decoding performance. As a result, speed is improved, and the performance increases by 25%, especially in graphics and multimedia content.
- Better security - the 64-bit version of Google Chrome can take advantage of the new security features that are included in Windows 8.1 and Windows 10. For example, it adds support for High Entropy ASLR (Address Space Layout Randomization), which provides an extra protection layer and a better defense against exploitation techniques. ASLR is based upon the low chance of an attacker guessing the locations of randomly placed areas. Security is increased by increasing the search space. Thus, address space randomization is more efficient when more entropy (disorder) is present in the random offsets. This prevents an attacker from reliably jumping to a particular exploited function in memory. The extra bits force the software to use all the resources to obtain maximum defense, improving existing security features.
- Improved stability - 64-bit rendering engines are almost twice as stable as the 32-bit engines, when handling web content. In particular, the crash rate for the rendering process is nearly 50% smaller than that of the 32-bit version of Google Chrome.
Later on, in late 2016, Google published another blog post in which they announced that the 64-bit Chrome has started using Microsoft's Profile Guided Optimization (PGO) technology, which makes Chrome up to 15% faster on Windows, as of version 53. However, you get the same boost if you are using the 32-bit, but only in its version 54 or newer.
Conclusion - Google Chrome 64-bit is worth using
It is safe to say that, when using the 64-bit version of Google Chrome, most users will not feel any difference in their web browsing experience. Performance-wise, our tests have shown that the differences are there to be found. However, they are still probably too small to be felt in daily use. On the other hand, there's also the RAM memory consumption factor to consider. As the 64-bit Google Chrome eats roughly twice as much memory as its 32-bit version does, it may be a tough pill to swallow for people who use lower end devices. However, in the end, we believe that the additional benefits such as the improved stability and security make this upgrade worthwhile. This is especially true if you watch lots of high-definition videos or you play games in your web browser. If you want to switch to the 64-bit version of Google Chrome today, go to this page and download it from there.
