Investigate performance of RIABench benchmark

RESOLVED INCOMPLETE

Status

Core Graveyard
Tracking
P4
normal
RESOLVED INCOMPLETE
5 years ago
2 years ago

People

(Reporter: cpeterson, Unassigned)

Tracking

(Depends on: 3 bugs, Blocks: 1 bug, {perf})

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

5 years ago
RIABench is one of the benchmarks from Tom's Hardware Guide's Web Browser Grand Prix:

http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-6.html

http://www.timo-ernst.net/misc/riabench-start/

The test cases:

 * Primetest
 * Prime factorization
 * 3D-Test
 * JPEG encoding test
 * MD5 hashing test
 * Random key generator test
 * Run-length encoding test (bug 851064)
 * 2D-Test (bug 851062)
 * Memory management test
 * Focus-tests
(Reporter)

Comment 1

5 years ago
On my MacBook Pro, Nightly 28 handily beats Chrome 30 on many RIABench tests. \o/

Firefox and Chrome are tied on the Primetest and Prime Factorization tests.
Keywords: perf
Priority: -- → P4
(In reply to Chris Peterson (:cpeterson) from comment #1)
> On my MacBook Pro, Nightly 28 handily beats Chrome 30 on many RIABench
> tests. \o/

When looking to the scores on WBGP with FF19 we were also beating chrome on most tests. The reason we didn't come out as first was the "Run-length encoding test" that was way slower. That's the reason I looked into this and this has been addressed in FF24. So RIABench shouldn't need much attention, right?
(Reporter)

Comment 3

5 years ago
Hannes: I agree that RIABench does not need much attention. I filed this bug mostly for completeness with all the benchmarks used by WBGP. <:)

Bug 851062 says we are much slower than Chrome on the Windows drawing tests.
(Reporter)

Updated

5 years ago
Depends on: 940823
(Reporter)

Updated

5 years ago
Depends on: 940827

Comment 4

2 years ago
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE.
If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work
being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

2 years ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.