41–50 of 87 posts
Browser vendors talk about benchmarks all the time but what really matters to me is startup and closing times; here Chrome really shines and FF3.6 is slow as hell. It's probably about perception; maybe the browser should show a window even if it's not really ready (and maybe there is a problem with plugins and add-ons that need to initialize themselves, etc.) Anyway, how is FF4b7 doing in this regard...?
Earlier quoted context omitted.
JS speed has improved so much recently due to optimisations like JIT (Just In Time compiling). There will be an upper limit eventually but we haven't hit it yet. It's damn fast but still a high-level interpreted language - time is taken for a program in the browser to compile it on the fly and run. It wont hit the speed of well written C code, but most things don't need that speed anyway.
I was browsing the language shootout the other day and came across the page for the regex test. I'm not sure how it's doing it or if something is wrong with the test but V8 is outperforming everything else, including C. That's the only test it leads though. Here are the results: http://shootout.alioth.debian.org/u32/performance.php?test=r... Also worth noting that TraceMonkey isn't too far behind. Does anyone know wh…
Browser vendors talk about benchmarks all the time but what really matters to me is startup and closing times; here Chrome really shines and FF3.6 is slow as hell. It's probably about perception; maybe the browser should show a window even if it's not really ready (and maybe there is a problem with plugins and add-ons that need to initialize themselves, etc.) Anyway, how is FF4b7 doing in this regard...?
Browser vendors talk about benchmarks all the time but what really matters to me is startup and closing times; here Chrome really shines and FF3.6 is slow as hell. It's probably about perception; maybe the browser should show a window even if it's not really ready (and maybe there is a problem with plugins and add-ons that need to initialize themselves, etc.) Anyway, how is FF4b7 doing in this regard...?
Can anyone elaborate on the XPCOM improvements? I thought the plan was to get rid of XPCOM all together in firefox 4. Very nice set of improvements though. Not sure about firefox 4, but firefox 3 was a memory hog.
>... but firefox 3 was a memory hog. I really do not find Firefox 3 to be a memory hog at all. I find it to consume much less memory than Chrome running multiple tabs over a prolonged period of time. I have caught Chrome running way out of control with memory usage and nearly maxing out my page file. My usage generally has Firefox using between 300MB and 500MB or RAM depending on what I have open. The same usage on C…
Browser vendors talk about benchmarks all the time but what really matters to me is startup and closing times; here Chrome really shines and FF3.6 is slow as hell. It's probably about perception; maybe the browser should show a window even if it's not really ready (and maybe there is a problem with plugins and add-ons that need to initialize themselves, etc.) Anyway, how is FF4b7 doing in this regard...?
Bootup time used to matter to me but now my laptop always sleeps - and likewise, I very rarely close all my browser tabs so the startup time is not very important to me.
Browser vendors talk about benchmarks all the time but what really matters to me is startup and closing times; here Chrome really shines and FF3.6 is slow as hell. It's probably about perception; maybe the browser should show a window even if it's not really ready (and maybe there is a problem with plugins and add-ons that need to initialize themselves, etc.) Anyway, how is FF4b7 doing in this regard...?
Strange, how often do you open/close your browser?
Nice, although I need Netflix & Firebug to work before I upgrade.