Hvad er din yndlingswebbrowser? Bruger^(Are) du tilfældigvis Google Chrome ? Bruger du Chrome 64-bit eller Chrome 32-bit? Hvis du stadig bruger 32-bit-versionen, men din Windows er 64-bit, bør du overveje også at skifte til 64-bit Google Chrome . Undrer du dig over, hvad der er bedst, eller hurtigst, eller det med de mindste systemkrav? Vi spurgte os selv alt det, så vi besluttede at få svar på disse spørgsmål. Vi kørte adskillige benchmarks, vi målte RAM -forbrug, vi gennemsøgte nettet for information, og vi endte med denne artikel. Hvis du vil vide, hvad der er forskellen mellem 64-bit og 32-bit versionerne af Google Chrome , så læs videre:

Google Chrome 64-bit vs. 32-bit - Ydeevne i benchmarks

Vi startede med at teste de to versioner af Googles^(Google) webbrowser i adskillige benchmarkingværktøjer: HTML5 test , JetStream 1.1 , Peacekeeper , Basemark Web 3.0 , Octane 2.0 og MotionMark 1.0 . Hvert benchmark undtagen HTML5 -testen blev kørt tre gange, og vi registrerede den gennemsnitlige score. Maskinen, vi brugte til at teste, er en mellemklassecomputer med gennemsnitlig ydeevne efter nutidens standarder: AMD FX8350- processor, der kører på 4,0 GHz , 8 GB DDR3 ved 2133 MHz og et AMD Radeon R9 270X -videokort med 2 GB GDDR5hukommelse. Vi brugte Windows 10 Professional version 1703 med Creators Update .

HTML5-testresultatet^{(HTML5 test)} er en indikation af, hvor godt din browser understøtter HTML5 - standarden og dens relaterede specifikationer. Som du kan se på den følgende graf, tilbyder 64-bit versionen af ​​Google Chrome det samme niveau af understøttelse af HTML5 -standarden som 32-bit versionen. Dette kan forventes, da vi sammenligner forskellige versioner af den samme browser.

JetStream 1.1-^{(JetStream 1.1)} benchmark kører latency-tests, som måler, hvor hurtigt webapplikationer kan starte og rampe op til maksimal ydeevne og køre problemfrit uden afbrydelser. Den kører også gennemstrømningstests, som måler den vedvarende maksimale ydeevne af webapplikationer. De højeste resultater betyder hurtigere hastighed og bedre ydeevne. Som du kan se på skærmbilledet nedenfor, er de resultater, vi fik, ikke så forskellige. 64-bit-versionen af ​​Google Chrome var dog 8 % hurtigere end 32-bit-versionen.

Dernæst brugte vi Peacekeeper benchmark , som er et ældre benchmark, men det er stadig relevant for nettet i dag. Peacekeeper måler browserens ydeevne ved at teste dens JavaScript - gengivelse og dens evne til at håndtere almindeligt anvendte JavaScript - funktioner. 64-bit versionen af ​​Google Chrome var vinderen igen med en forskel mellem score på 4 %.

Den næste test, vi brugte, var Basemark Web 3.0 . Den måler evnen til at gengive objekter i 2D og 3D og crunche flere CSS- operationer ad gangen. Den fortæller også, hvor godt browseren understøtter CSS3 , HTML5 , Flash og Silverlight og hvor hurtigt browseren indlæser sider og sender anmodninger. I denne test var 64-bit versionen af ​​Google Chrome igen vinderen med en margin på næsten 6 %.

Octane 2.0 er et benchmark udviklet og vedligeholdt af Google selv. Dette benchmark måler JavaScript -ydeevnen for din webbrowser, og det kører en række tests, som dækker de mest almindelige brugssager, der findes på nettet. 64-bit-versionen af ​​Google Chrome formåede at få et resultat, der er næsten 7 % bedre end hvad 32-bit-versionen opnåede.

Endelig kørte vi også MotionMark , et benchmark, der fokuserer på grafisk ydeevne. Testene, den kører, er visuelt rige og designet til at understrege det grafiske system frem for JavaScript . Google Chrome 64-bit havde en ydeevne, der var 16 % bedre end dens 32-bit version.

Google Chrome 64-bit vs. 32-bit - RAM-forbrug

RAM -hukommelsesforbrug er lige så vigtigt som JavaScript eller grafikydeevne, især hvis du bruger en langsommere enhed med mindre RAM end gennemsnittet. For at se, hvor meget RAM -hukommelse der kræves af Google Chromes^{(Google Chrome)} 64-bit og 32-bit versioner, gjorde vi følgende:

• Vi brugte en computer i mellemklassen med en gennemsnitlig ydeevne efter nutidens standarder: AMD FX8350- processor, der kører ved 4,0 GHz , 8 GB DDR3 ved 2133MHz og et AMD Radeon R9 270X -videokort med 2 GB GDDR5 -hukommelse, alt sammen kører på Windows 10 Professional - versionen 1703 med Creators Update .
• Vi installerede Google Chrome 64-bit og derefter Google Chrome 32-bit , og for hver af dem åbnede vi de samme faner. Vi forsøgte at kopiere et scenarie fra det virkelige liv, så vi åbnede faner for hver af disse websteder: Gmail , Facebook , CNN , YouTube , BoredPanda og Digital Citizen - 2 faner for os. 🙂
• For hver hjemmeside, vi åbnede, rullede vi deres indhold så meget som muligt. Det betød, at Facebook var nødt til at blive ved med at indlæse indhold i sit nyhedsfeed, indtil det ikke havde noget at vise mere, og stoppede med en sjov besked om "Du vil have flere historier i nyhedsfeeden, hvis du tilføjer flere venner." ^{("You'll have more stories in News Feed if you add more friends.")}I tilfældet med YouTube indlæste vi det ikke bare, men vi afspillede også en video i det.

Efter vores mening, og vi håber, at også i din, bør alt ovenstående skabe en situation så tæt på virkeligheden som muligt. For at kontrollere, hvor meget RAM -hukommelse der bruges af Google Chrome , brugte vi dens Task Manager- funktion. Det skyldes, at det viser mere detaljerede oplysninger om hver fane, der åbnes i Google Chrome , end de oplysninger, du får i Task Manager , der findes i Windows.

Da vi brugte 64-bit-versionen, spiste Google Chrome hele 1,19 GB RAM -hukommelse for at indlæse alle de faner, vi opregnede ovenfor.

Da vi brugte dens 32-bit version, behøvede Google Chrome kun 634 MB RAM -hukommelse for at indlæse alle disse faner.

Som du kan se, har 64-bit-versionen af ​​Google Chrome^{(Google Chrome)} i virkelige situationer brug for næsten dobbelt så meget RAM -hukommelse, som 32-bit-versionen kræver. Desværre er det ikke gode nyheder for folk, der bruger low-end enheder, med ikke nok RAM -hukommelse.

Andre ting at overveje om Google Chrome 64-bit vs. 32-bit med hensyn til hastighed, sikkerhed og stabilitet

Da Google annoncerede lanceringen^{(Google announced the launch)} af ​​64-bit-versionen af ​​Chrome i 2014, delte de også nogle oplysninger om, hvad brugerne skulle forvente af den. Udover den lidt hurtigere ydeevne, vi har målt i benchmarks, er der også fordele, som ikke kan måles med sådanne testværktøjer:

• Forbedret hastighed ved håndtering af grafik og video^{(Improved speed when dealing with graphics and video)} - 64-bit versionen af ​​Google Chrome forbedrer hastigheden af ​​grafik og video, inklusive High Definition YouTube - videoer. For eksempel viser VP9- codec'et, der bruges i High Definition YouTube- videoer, en forbedring på 15 % i afkodningsydelsen. Som et resultat er hastigheden forbedret, og ydeevnen øges med 25 %, især inden for grafik og multimedieindhold.
• Bedre sikkerhed^{(Better security)} - 64-bit versionen af ​​Google Chrome kan drage fordel af de nye sikkerhedsfunktioner, der er inkluderet i Windows 8.1 og Windows 10 . For eksempel tilføjer den understøttelse af High Entropy ASLR (Address Space Layout Randomization ), som giver et ekstra beskyttelseslag og et bedre forsvar mod udnyttelsesteknikker. ASLR er baseret på den lave chance for, at en angriber gætter placeringen af ​​tilfældigt placerede områder. Sikkerhed^(Security)øges ved at øge søgerummet. Således er randomisering af adresserum mere effektiv, når mere entropi (uorden) er til stede i de tilfældige forskydninger. Dette forhindrer en angriber i at hoppe til en bestemt udnyttet funktion i hukommelsen. De ekstra bits tvinger softwaren til at bruge alle ressourcer til at opnå maksimalt forsvar, hvilket forbedrer eksisterende sikkerhedsfunktioner.
• Forbedret stabilitet^{(Improved stability)} - 64-bit-gengivelsesmotorer er næsten dobbelt så stabile som 32-bit-motorer, når de håndterer webindhold. Især er nedbrudsraten for gengivelsesprocessen næsten 50 % mindre end for 32-bit-versionen af ​​Google Chrome .

Senere, i slutningen af ​​2016, offentliggjorde Google endnu et ^(Google)blogindlæg^{(blog post)} , hvori de annoncerede, at 64-bit Chrome er begyndt at bruge Microsofts ^(Microsoft)Profile Guided Optimization ( PGO ) teknologi, som gør Chrome op til 15 % hurtigere på Windows fra versionen 53. Du får dog det samme boost, hvis du bruger 32-bit, men kun i dens version 54 eller nyere.

Konklusion^(Conclusion) - Google Chrome 64-bit er værd at bruge

Det er sikkert at sige, at når de bruger 64-bit-versionen af ​​Google Chrome , vil de fleste brugere ikke mærke nogen forskel i deres web-browsing-oplevelse. Ydelsesmæssigt har vores test vist, at forskellene er til at finde. Dog er de nok stadig for små til at kunne mærkes i daglig brug. På den anden side er der også RAM -hukommelsesforbrugsfaktoren at overveje. Som 64-bit Google Chromespiser omtrent dobbelt så meget hukommelse som dens 32-bit version gør, kan det være en svær pille at sluge for folk, der bruger lavere ende enheder. Men i sidste ende mener vi, at de yderligere fordele såsom den forbedrede stabilitet og sikkerhed gør denne opgradering umagen værd. Dette gælder især, hvis du ser mange high-definition videoer, eller du spiller spil i din webbrowser. Hvis du vil skifte til 64-bit versionen af ​​Google Chrome i dag, skal du gå til denne side^(page) og downloade den derfra.

Google Chrome 64-bit: Is it better than the 32-bit version?

What's your fаvoritе web browser? Are you, by any chanсe, using Goоgle Chrоme? Do yоu use Chrome 64-bіt or Chrome 32-bit? If you are still using the 32-bit version but your Windows is 64-bit, you should cоnsider switching to thе 64-bit Google Chrome as well. Do уou wonder which is best, or the fastest, or the one with the lesser system requirements? We asked ourselveѕ all that too, so we decided to get an аnswer tо these questions. Wе ran several benchmarks, we measured RAM consumption, we sсоured the web for infоrmatіon, and we ended up with this аrticle. If you want to know what's different between the 64-bit and 32-bit vеrsions 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.

Related posts

• Chrome 64-bit eller Chrome 32-bit: Download den version, du ønsker, til Windows 10 eller ældre

• Om InPrivate og Incognito. Hvad er privat browsing? Hvilken browser er den bedste?

• Sæt Chrome og andre browsere i fuld skærm (Edge, Firefox og Opera)

• Hvilken browser vil få dit batteri til at holde længere i Windows 10?

• Sådan indstilles en proxyserver i Chrome, Firefox, Edge og Opera

• Sådan downloades og installeres iCloud til Windows

• 7 måder, hvorpå browsere bør forbedre privat browsing (inkognito, InPrivate osv.)

• Sådan udskrives en artikel uden annoncer i alle større browsere -

• Sådan aktiverer du Java i alle de store webbrowsere

• Sådan inficerer du din Windows-pc, mens du surfer på nettet efter gratis ting

• Sådan bruger du Skype på Windows 10 som en Pro

• Sådan henter du filer med OneDrive fra en Windows-pc

• 5 sjove og nørdede ting, du kan lave med Telnet-klienten

• Browser Wars: Hvilken ydeevne leverer Internet Explorer 11?

• Sådan forhindrer du Chrome i at bede om at gemme adgangskoder -

• Sådan sætter du Google Chrome i mørk tilstand -

• Sådan ændres søgemaskinen på Chrome til Windows, macOS, Android og iOS -

• Sådan deler du fra OneDrive ved hjælp af midlertidige links, i Windows, Android eller en webbrowser

• Sådan slår du Chrome-meddelelser fra: Alt hvad du behøver at vide -

• Hvilken version af Chrome har jeg? 6 måder at finde ud af -