Summary: | Sunspider gets progressively slower | ||
---|---|---|---|
Product: | WebKit | Reporter: | Gavin Sherlock <gsherloc> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WORKSFORME | ||
Severity: | Normal | CC: | ap, barraclough, prashantnevase, puurtuur |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Mac | ||
OS: | OS X 10.5 | ||
URL: | http://webkit.org/perf/sunspider-0.9/sunspider.html |
Description
Gavin Sherlock
2008-05-25 22:57:23 PDT
Note, this behavior is also observed under 3.1.1 (5525.18). The slow down as a percentage and in terms of milliseconds is not as extreme, though I don't know whether that qualifies this as a regression. A comparison of the 1st and 5th runs under 3.1.1, on the same machine as I used for r34130, is below: TEST COMPARISON FROM TO DETAILS ============================================================================= ** TOTAL **: *1.02x as slow* 2858.6ms +/- 0.3% 2923.8ms +/- 0.3% significant ============================================================================= 3d: *1.04x as slow* 350.4ms +/- 0.8% 364.2ms +/- 0.8% significant cube: *1.09x as slow* 115.8ms +/- 2.1% 125.8ms +/- 0.8% significant morph: - 120.4ms +/- 1.6% 119.2ms +/- 1.4% raytrace: *1.04x as slow* 114.2ms +/- 0.9% 119.2ms +/- 0.9% significant access: *1.03x as slow* 444.4ms +/- 0.7% 456.8ms +/- 0.2% significant binary-trees: *1.03x as slow* 60.4ms +/- 2.3% 62.4ms +/- 1.1% significant fannkuch: ?? 201.6ms +/- 1.5% 203.8ms +/- 0.7% not conclusive: might be *1.01x as slow* nbody: *1.07x as slow* 129.4ms +/- 1.1% 138.2ms +/- 0.4% significant nsieve: - 53.0ms +/- 4.1% 52.4ms +/- 1.3% bitops: ?? 388.2ms +/- 1.2% 388.8ms +/- 0.7% not conclusive: might be *1.00x as slow* 3bit-bits-in-byte: - 57.6ms +/- 1.2% 57.0ms +/- 2.2% bits-in-byte: ?? 85.4ms +/- 2.4% 85.6ms +/- 1.3% not conclusive: might be *1.00x as slow* bitwise-and: - 146.4ms +/- 1.5% 145.8ms +/- 2.1% nsieve-bits: *1.02x as slow* 98.8ms +/- 1.1% 100.4ms +/- 0.7% significant controlflow: ?? 75.2ms +/- 0.7% 75.6ms +/- 0.9% not conclusive: might be *1.01x as slow* recursive: ?? 75.2ms +/- 0.7% 75.6ms +/- 0.9% not conclusive: might be *1.01x as slow* crypto: *1.02x as slow* 202.0ms +/- 0.4% 205.8ms +/- 0.5% significant aes: *1.02x as slow* 66.8ms +/- 0.8% 68.0ms +/- 0.0% significant md5: *1.02x as slow* 67.4ms +/- 1.0% 69.0ms +/- 0.0% significant sha1: *1.01x as slow* 67.8ms +/- 0.8% 68.8ms +/- 1.5% significant date: *1.02x as slow* 254.8ms +/- 0.2% 259.0ms +/- 0.5% significant format-tofte: *1.01x as slow* 116.8ms +/- 0.5% 118.2ms +/- 0.9% significant format-xparb: *1.02x as slow* 138.0ms +/- 0.0% 140.8ms +/- 0.4% significant math: *1.04x as slow* 391.4ms +/- 1.1% 407.4ms +/- 0.6% significant cordic: *1.04x as slow* 152.0ms +/- 1.6% 157.4ms +/- 0.7% significant partial-sums: *1.04x as slow* 167.0ms +/- 1.1% 173.4ms +/- 0.8% significant spectral-norm: *1.06x as slow* 72.4ms +/- 0.9% 76.6ms +/- 0.9% significant regexp: - 185.0ms +/- 0.8% 184.2ms +/- 0.6% dna: - 185.0ms +/- 0.8% 184.2ms +/- 0.6% string: *1.03x as slow* 567.2ms +/- 0.2% 582.0ms +/- 0.6% significant base64: *1.04x as slow* 84.6ms +/- 1.7% 87.8ms +/- 1.2% significant fasta: *1.01x as slow* 153.4ms +/- 0.4% 154.6ms +/- 0.7% significant tagcloud: *1.04x as slow* 113.6ms +/- 0.6% 118.0ms +/- 0.7% significant unpack-code: *1.01x as slow* 114.4ms +/- 1.2% 116.0ms +/- 0.8% significant validate-input: *1.04x as slow* 101.2ms +/- 0.5% 105.6ms +/- 2.4% significant Progressing memory fragmentation is what comes to mind first, but ideally, this shouldn't happen, of course. I ran SunSpider 10 times and got these results: 190.5 190.4 191.4 187.9 189.7 187.4 192.9 187.9 190.4 187.1 I can't repro a pattern of a regression over time. *** Bug 19369 has been marked as a duplicate of this bug. *** |