المساعد الشخصي الرقمي

مشاهدة النسخة كاملة : Google Improving Chrome for OS X Performance to Better Rival Safari [Mac Blog]


ahlam1399
06-13-2015, 04:13 AM
http://cdn.macrumors.com/article-new/2015/05/Google_Chrome_Material_Icon-450x450-250x250.jpgGoogle senior software engineer Peter Kasting this week an**unced (https://plus.google.com/+PeterKasting/posts/GpL63A1K2TF) that his team has been working to address Chrome for OS X battery hog complaints by improving the performance of the browser on Mac, especially in areas where Safari appears to do better (via iPhoneHacks (http://www.iphonehacks.com/2015/06/google-working-improvements-address-chromes-battery-hog-complaints-mac.html)).

Chrome for OS X has received multiple under the hood improvements that should result in faster performance and longer battery life while browsing. The browser, for example, **w requires significantly less CPU usage when loading the Google search results page and various other websites.

The other technical changes to Chrome for OS X are outlined as follows:"The team has been working on addressing this; here are some cases that have recently been improved on trunk:

http://crbug.com/460102

Before: Renderers for background tabs had the same priority as for foreground tabs.
**w: Renderers for background tabs get a lower priority, reducing idle wakeups on various perf test, in some cases by significant amounts (e.g. 50% on one test).

http://crbug.com/485371

Before: On a Google search results page, using Safari's user agent to get the same content that Safari would, Chrome incurs ~390 wakes over 30s and 0.3% CPU usage vs. Safari?s 120 wakes over 30s and 0.1% CPU usage.
**w: 66% reduction in both timer firings and CPU use. Chrome is **w incurring ~120 wakes over 30s and 0.1% CPU use, on par with Safari.

http://crbug.com/489936

Before: On capitalone.com, Chromium incurs ~1010 wakeups over 30s vs. Safari's ~490 wakes.
**w: ~30% reduction in timer firings. Chrome is **w incurring ~721 wakeups over 30s.

http://crbug.com/493350

Before: On amazon.com, Chromium incurs 768 wakups over 30s and consumes ~0.7% CPU vs. Safari's 312 wakes over 30s and ~0.1% CPU.
**w: ~59% reduction in timer firings and ~70% reduction in CPU use. Chrome is **w incurring ~316 wakeups over 30s, and 0.2% CPU use, on par with Safari at 312 wakes, and 0.1% CPU use."Many of the changes will first appear in Chromium before going live on Chrome for OS X.http://rss.feedsportal.com/c/35070/f/648326/s/472dca14/sc/28/mf.gif


http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/1/rc.img (http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/1/rc.htm)
http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/2/rc.img (http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/2/rc.htm)
http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/3/rc.img (http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/rc/3/rc.htm)

http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/a2.img (http://da.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/a2.htm)
http://adchoice.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/ach.img (http://adchoice.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/ach.htm)http://pi.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/a2t.imghttp://pi2.feedsportal.com/r/231041721731/u/49/f/648326/c/35070/s/472dca14/sc/28/a2t2.img http://feeds.feedburner.com/~ff/MacRumors-All?d=yIl2AUoC8zA (http://feeds.macrumors.com/~ff/MacRumors-All?a=7D0bbtT4ltw:pb6_Nffq4vU:yIl2AUoC8zA) http://feeds.feedburner.com/~ff/MacRumors-All?d=6W8y8wAjSf4 (http://feeds.macrumors.com/~ff/MacRumors-All?a=7D0bbtT4ltw:pb6_Nffq4vU:6W8y8wAjSf4)
http://feeds.feedburner.com/~r/MacRumors-All/~4/7D0bbtT4ltw

أكثر... (http://www.macrumors.com/2015/06/12/chrome-os-x-performance-improvements-safari/)