Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #17986
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!news.albasani.net!.POSTED!not-for-mail |
|---|---|
| From | Stefan Weiss <krewecherl@gmail.com> |
| Newsgroups | comp.lang.javascript |
| Subject | Re: Mysterious slowdown in Chromium |
| Date | Sun, 06 Jan 2013 17:33:19 +0100 |
| Organization | albasani.net |
| Lines | 45 |
| Message-ID | <kcc90f$tro$1@news.albasani.net> (permalink) |
| References | <kcc0nh$ckn$1@news.albasani.net> <kcc528$3m3$1@dont-email.me> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8 |
| Content-Transfer-Encoding | 7bit |
| X-Trace | news.albasani.net wv6r1ipAooT5nxL6XZ4xXugmoxR2ffb/I8O2a/Wz5Jkuy/5aJpUg0e3xWrPatR6ai69dRJlGYt4ABwDuKqfmnfbsgq66UggoaOhI9uceHYontkzHAjvVy3y6dn8kvkz+ |
| NNTP-Posting-Date | Sun, 6 Jan 2013 16:33:19 +0000 (UTC) |
| Injection-Info | news.albasani.net; logging-data="Xc+lfvoY0kgS//zHm/BH/Iv6ymJh4VuBrDvRuxBwnlV+SsOdrX59x4HkA3jZvY7aD7k1NRwUUnUq1WOSCIH12NgXG8HNu7govywSdyLFUF1+aJUgd2DYqQRs3TWvduSe"; mail-complaints-to="abuse@albasani.net" |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 |
| In-Reply-To | <kcc528$3m3$1@dont-email.me> |
| Cancel-Lock | sha1:TXuJ5nTGZCPOWMEBGAJpLTZLawY= |
| Xref | csiph.com comp.lang.javascript:17986 |
Show key headers only | View raw
On 2013-01-06 16:25, Gregor Kofler wrote:
> Checked this on Chromium 22 (Ubuntu AMD64) in the web developer console
>
> (function bench() {
> function test() {}
> var runs = 10000000, // adjust as needed
> t0 = +new Date();
> while (runs--) test();
> console.log((+new Date() - t0) + "ms");
> })();
>
> Execution time stays constant with 90ms to 95ms.
Interesting. Running this here always takes around 2650ms. It appears
that function expressions and function declarations exhibit the problem
differently:
function bench2() { ... as before ... }
var bench3 = function () { ... as before ... };
bench3(); -> 2655ms
bench3(); -> 2652ms
bench2(); -> 18ms
bench2(); -> 59ms
bench2(); -> 64ms
bench2(); -> 62ms
bench2(); -> 60ms
bench2(); -> 57ms
bench2(); -> 61ms
bench2(); -> 303ms
bench2(); -> 303ms
bench2(); -> 300ms
bench2(); -> 301ms
bench2(); -> 301ms
bench2(); -> 2653ms
bench3(); -> 2648ms
bench3(); -> 2652ms
Must be an old bug in my Chromium version. I guess I won't be doing any
more benchmarks until I can find the time to upgrade my OS :)
Thank you (and GGolf and Scott) for testing!
- stefan
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Mysterious slowdown in Chromium Stefan Weiss <krewecherl@gmail.com> - 2013-01-06 15:12 +0100
Re: Mysterious slowdown in Chromium GGolf <invalid@invalid.com> - 2013-01-06 20:22 +0530
Re: Mysterious slowdown in Chromium Gregor Kofler <usenet@gregorkofler.com> - 2013-01-06 16:25 +0100
Re: Mysterious slowdown in Chromium Stefan Weiss <krewecherl@gmail.com> - 2013-01-06 17:33 +0100
Re: Mysterious slowdown in Chromium Cezary Tomczyk <cezary.tomczyk@gmail.com> - 2013-01-06 23:44 +0100
Re: Mysterious slowdown in Chromium Scott Sauyet <scott.sauyet@gmail.com> - 2013-01-06 08:19 -0800
Re: Mysterious slowdown in Chromium Patricia Shanahan <pats@acm.org> - 2013-01-06 08:32 -0800
csiph-web