Posts Tagged ‘chrome’
Some elementary Chrome benchmarking
I ran the V8 Benchmark Suite on all browsers installed on one of my colleagues office PC. Given below are the results…bigger the final score, better the performance is what the benchmark page says
|
Browser |
Version |
Total Score |
|
Internet Explorer |
6.0.2900.2180.xpsp_sp2_rtm.040803-2158 |
22 |
|
Safari |
3.0.4 (523.15) |
51 |
|
Flock |
2.0b1 |
116 |
|
Firefox |
3.0.1 |
126 |
|
Chrome |
Official Build 1583 |
1288 |
Some basic hygeine factors were taken into consideration while testing…nothing professional, but I hope the numbers make sense? You can run the benchmarks here and check your results.
Robert O’Callahan posts some interesting issues with Chrome
Mozilla hacker Robert O’Callahan highlights some interesting issues concerning Chrome in this post…
– Multiple processes rendering to a single window on Mac. There’s no supported way to do that AFAIK. From your docs (great docs by the way!), it seems you don’t have an answer there yet either.
– Separate-process plugins rendering in windowless mode. I haven’t had a chance to grovel through your code yet, but I didn’t see anything in the docs about it. Sounds especially tricky in Chrome since, if I understand correctly, all interaction between the plugin and the page is routed through the master browser process.
– Synchronous two-way script interaction between the page and a separate-process plugin seems like it’s hard to make performant.
– Running different-origin iframes in separate processes sounds hard; the interaction between iframes and their hosts is complex and bears on Web compatibility. (And the interaction gets more complicated with HTML5 “seamless” iframes.) But it really has to be solved, I think, because otherwise a compromised renderer process can violate the iframe security boundary — a gaping hole in the security architecture.
Would be interesting to see how google answers these.
Maximize Content, Minimize Chrome…
Just started using Google’s latest app – the Chrome Browser. I loved the minimalist design of the browser; it lives up to the “Maximize Content and Minimize Chrome” philosophy talked about in their The story behind Google Chrome video.
But I was a little puzzled by Chrome’s resource utilization. For all the speed that Google has been talking about, the browser was stuggling real hard when I started switching between just about 10 tabs.
Doesn’t look like Google will come out with a browser that bites the dust so easily. Something must be wrong with my config…or the sites i picked up…I’ll check it out later…probably next week.
One thing I want to do for sure is compare Flock with Chrome…both claim to be for the “new” web, and both are in beta. I don’t have any complaints about Flock till date.