Release the Kraken (Benchmark) - post your results

fitten

Ars Legatus Legionis
52,250
Subscriptor++
And that's when you know your precious high-end is getting beat:

===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 469.2ms +/- 9.2%

(Ryzen 5950X on latest Chrome.)

That tells me I have to upgrade in 2 or so years. Thanks for the heads-up ;)

Here's my Geekbench 6 for the machine that is being replaced: https://browser.geekbench.com/v6/cpu/4321061

And the 12100 system: https://browser.geekbench.com/v6/cpu/4316086

I was looking at stuff and realized that the 12100 system had defaulted to DDR4-2400! (I had bought the cheapest, which was DDR4-3600). So I changed that and reran. I also think I saw somewhere where it was limited to 75W (Intel website says 89W max) but I'm not going to worry about that. The memory change has the single threaded benchmark roughly the same but it got a little boost on the multithreaded side.


I ran it on my 10700K system (stock speeds) and had a little chuckle... the 12100 beats it pretty well at single threaded and even beats it a little at multithreaded... but I also have a bunch of stuff running on the 10700K... nothing major but stuff like Skype, Discord, and some things that might cause a little bit of perf drop. It's also running Win11 rather than Linux.


I'm planning on upgrading the Win11 machine maybe this year after the new stuff comes out (end of year, early next year) if it's a good boost like rumors say.

You should score a bit higher in that, at least the multi-core stuff ;)
 
Last edited:
  • Like
Reactions: hansmuff

roccovw

Seniorius Lurkius
33
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 339.6ms +/- 1.7%
-----------------------------------------------

ai: 33.5ms +/- 12.7%
astar: 33.5ms +/- 12.7%

audio: 81.9ms +/- 2.6%
beat-detection: 18.4ms +/- 3.8%
dft: 27.9ms +/- 3.9%
fft: 14.1ms +/- 6.5%
oscillator: 21.5ms +/- 1.8%

imaging: 127.5ms +/- 0.5%
gaussian-blur: 48.1ms +/- 0.5%
darkroom: 57.9ms +/- 0.7%
desaturate: 21.5ms +/- 1.8%

json: 19.6ms +/- 2.5%
parse-financial: 8.8ms +/- 3.4%
stringify-tinderbox: 10.8ms +/- 2.8%

stanford: 77.1ms +/- 4.3%
crypto-aes: 19.9ms +/- 2.0%
crypto-ccm: 24.5ms +/- 1.5%
crypto-pbkdf2: 22.9ms +/- 13.4%
crypto-sha256-iterative: 9.8ms +/- 3.1%

14700KF
TUF 4070 OC
MS Edge
 
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 594.9ms +/- 6.8%
-----------------------------------------------

ai: 64.1ms +/- 22.4%
astar: 64.1ms +/- 22.4%

audio: 170.0ms +/- 6.3%
beat-detection: 48.2ms +/- 4.4%
dft: 39.4ms +/- 6.3%
fft: 40.4ms +/- 4.0%
oscillator: 42.0ms +/- 23.8%

imaging: 205.1ms +/- 8.3%
gaussian-blur: 69.8ms +/- 4.5%
darkroom: 66.8ms +/- 1.1%
desaturate: 68.5ms +/- 26.2%

json: 33.6ms +/- 25.3%
parse-financial: 18.0ms +/- 41.6%
stringify-tinderbox: 15.6ms +/- 20.3%

stanford: 122.1ms +/- 17.2%
crypto-aes: 36.1ms +/- 17.0%
crypto-ccm: 26.2ms +/- 18.6%
crypto-pbkdf2: 39.2ms +/- 19.2%
crypto-sha256-iterative: 20.6ms +/- 46.5%

i5-13400
GTX 1650 Super
Firefox
 
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 330.7ms +/- 0.4%
-----------------------------------------------

ai: 29.4ms +/- 1.3%
astar: 29.4ms +/- 1.3%

audio: 80.6ms +/- 1.3%
beat-detection: 17.8ms +/- 1.7%
dft: 26.6ms +/- 2.6%
fft: 13.9ms +/- 2.9%
oscillator: 22.3ms +/- 1.5%

imaging: 125.0ms +/- 0.7%
gaussian-blur: 47.7ms +/- 1.0%
darkroom: 57.9ms +/- 0.7%
desaturate: 19.4ms +/- 1.9%

json: 20.0ms +/- 1.7%
parse-financial: 8.8ms +/- 3.4%
stringify-tinderbox: 11.2ms +/- 2.7%

stanford: 75.7ms +/- 1.4%
crypto-aes: 19.7ms +/- 3.8%
crypto-ccm: 24.7ms +/- 1.4%
crypto-pbkdf2: 21.8ms +/- 1.4%
crypto-sha256-iterative: 9.5ms +/- 4.0%

i7-14700K
integrated graphics
MS Edge
 
  • Like
Reactions: owdi

Claropus

Wise, Aged Ars Veteran
112
Total: 510.1ms +/- 2.5%
-----------------------------------------------

ai: 139.0ms +/- 9.4%
astar: 139.0ms +/- 9.4%

audio: 140.4ms +/- 0.7%
beat-detection: 36.4ms +/- 1.0%
dft: 41.0ms +/- 1.4%
fft: 24.8ms +/- 2.3%
oscillator: 38.2ms +/- 0.8%

imaging: 115.6ms +/- 1.3%
gaussian-blur: 39.5ms +/- 3.5%
darkroom: 39.9ms +/- 0.6%
desaturate: 36.2ms +/- 1.2%

json: 22.0ms +/- 2.2%
parse-financial: 11.0ms +/- 3.1%
stringify-tinderbox: 11.0ms +/- 4.3%

stanford: 93.1ms +/- 1.3%
crypto-aes: 28.8ms +/- 1.6%
crypto-ccm: 21.1ms +/- 3.0%
crypto-pbkdf2: 30.5ms +/- 1.7%
crypto-sha256-iterative: 12.7ms +/- 2.7%

iPad Mini
A15b @ 2.9GHz
stock Safari
 

Claropus

Wise, Aged Ars Veteran
112
That's....impressive. I'm sure it's already been discussed, but is it Safari or is it the M1?
Apologies for replying a couple years late – I was kinda having fun going through the history (never really looked at this thread before). This may or may not be accurate, or not still accurate, but I recall reading about the unfair advantage Safari has. On Mac and iThings, it runs the JS engine in EL1, which assume means it can bypass MMU paging to get better performance. On iOS, all the browsers are/were required to use WebKit, and I think they all use the JS engine, but they call it at EL0: only Safari can use it at EL1. I could be completely off base on all this, but testing Windows Safari (if it is still around) might be illuminating.
 

teleos

Wise, Aged Ars Veteran
333
Apologies for replying a couple years late – I was kinda having fun going through the history (never really looked at this thread before). This may or may not be accurate, or not still accurate, but I recall reading about the unfair advantage Safari has. On Mac and iThings, it runs the JS engine in EL1, which assume means it can bypass MMU paging to get better performance. On iOS, all the browsers are/were required to use WebKit, and I think they all use the JS engine, but they call it at EL0: only Safari can use it at EL1. I could be completely off base on all this, but testing Windows Safari (if it is still around) might be illuminating.
Do you have a reference to this? This is the first time that I've heard that a JS engine runs in privileged mode.
 

Claropus

Wise, Aged Ars Veteran
112
Do you have a reference to this?

Thank you for calling me out.

I do apologize for posting incorrect information.

It appears that I heard a thing many years ago and transformed it in my head to a different thing. The engine that Safari was using did JITC and had a right to mark pages as executable (otherwise, JITC would be pointless), but that feature was withheld from other iOS browsers for obvious security reasons. Apple has refined something and/or the other (probably tightened API constraints) to allow other browsers access to the JITC engine, so the issue no longer exists.
 
  • Like
Reactions: teleos

fitten

Ars Legatus Legionis
52,250
Subscriptor++
Upgraded my Linux box to Ubuntu 24.04 LTS...
Homebrew Intel i3-12100, Asrock B760M-HDV/M.2 D4, 32GB DDR4 3200
Ubuntu Linux 24.04 LTS, Chrome Version 124.0.6367.91 (Official Build) (64-bit)


Code:
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total:                        457.7ms +/- 1.3%
-----------------------------------------------

  ai:                          39.9ms +/- 3.0%
    astar:                     39.9ms +/- 3.0%

  audio:                      116.2ms +/- 3.6%
    beat-detection:            26.9ms +/- 5.7%
    dft:                       36.2ms +/- 3.5%
    fft:                       20.3ms +/- 2.4%
    oscillator:                32.8ms +/- 12.5%

  imaging:                    170.7ms +/- 0.4%
    gaussian-blur:             62.9ms +/- 0.6%
    darkroom:                  77.2ms +/- 0.6%
    desaturate:                30.6ms +/- 1.2%

  json:                        23.0ms +/- 1.5%
    parse-financial:            9.7ms +/- 3.6%
    stringify-tinderbox:       13.3ms +/- 2.6%

  stanford:                   107.9ms +/- 3.4%
    crypto-aes:                30.1ms +/- 5.1%
    crypto-ccm:                34.5ms +/- 5.1%
    crypto-pbkdf2:             29.9ms +/- 2.9%
    crypto-sha256-iterative:   13.4ms +/- 7.2%

So pretty close to the original https://arstechnica.com/civis/threa...st-your-results.1189620/page-12#post-42488625
 
Last edited:
  • Like
Reactions: MadeInDex

Made in Hurry

Ars Praefectus
4,553
Subscriptor
Garage computer. Mint 21.3 Cinnamon
i5-2600 - Mozilla 125.0.2


Code:
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total:                       1481.6ms +/- 0.8%
-----------------------------------------------

  ai:                         174.7ms +/- 2.0%
    astar:                    174.7ms +/- 2.0%

  audio:                      515.9ms +/- 1.7%
    beat-detection:           130.2ms +/- 12.7%
    dft:                      152.6ms +/- 1.8%
    fft:                      111.5ms +/- 5.7%
    oscillator:               121.6ms +/- 11.4%

  imaging:                    491.9ms +/- 1.6%
    gaussian-blur:            182.6ms +/- 1.9%
    darkroom:                 138.8ms +/- 1.0%
    desaturate:               170.5ms +/- 3.6%

  json:                        55.5ms +/- 5.8%
    parse-financial:           28.6ms +/- 12.0%
    stringify-tinderbox:       26.9ms +/- 2.0%

  stanford:                   243.6ms +/- 2.2%
    crypto-aes:                70.5ms +/- 7.7%
    crypto-ccm:                49.8ms +/- 1.3%
    crypto-pbkdf2:             86.0ms +/- 2.0%
    crypto-sha256-iterative:   37.3ms +/- 2.6%
 

Aeonsim

Ars Scholae Palatinae
1,057
Subscriptor++
Some odder/older hardware, running outdated versions of Firefox so not directly comparable but still interesting.

Surface RT, Tegra 3 - FFX on Linux: 18423ms
EeePC 901, Atom N270 - FFX on Linux: 16182ms
Surface Book, i7-8650U - Windows Chrome: 848ms

And for something more modern:
AMD 5700X - Windows Chrome: 433ms
 

Made in Hurry

Ars Praefectus
4,553
Subscriptor
Chromium on the same box is much faster:

i5-2600 vanilla, i am seriously impressed.

Version 124.0.6367.118 (Official Build) for Linux Mint (64-bit)

Code:
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total:                       1203.3ms +/- 1.0%
-----------------------------------------------

  ai:                         119.3ms +/- 2.9%
    astar:                    119.3ms +/- 2.9%

  audio:                      338.5ms +/- 1.5%
    beat-detection:            71.4ms +/- 5.4%
    dft:                      153.9ms +/- 4.6%
    fft:                       50.5ms +/- 3.0%
    oscillator:                62.7ms +/- 1.6%

  imaging:                    452.0ms +/- 1.0%
    gaussian-blur:            165.1ms +/- 0.7%
    darkroom:                 202.4ms +/- 1.7%
    desaturate:                84.5ms +/- 1.4%

  json:                        58.6ms +/- 1.3%
    parse-financial:           30.2ms +/- 1.9%
    stringify-tinderbox:       28.4ms +/- 1.3%

  stanford:                   234.9ms +/- 2.8%
    crypto-aes:                61.6ms +/- 3.2%
    crypto-ccm:                74.7ms +/- 8.1%
    crypto-pbkdf2:             66.2ms +/- 3.1%
    crypto-sha256-iterative:   32.4ms +/- 3.5%
 

Aeonsim

Ars Scholae Palatinae
1,057
Subscriptor++
Some odder/older hardware, running outdated versions of Firefox so not directly comparable but still interesting.

EeePC 901, Atom N270 - FFX on Linux: 16182ms
Switching to Chromium is about 12% faster for the EeePC.

EeePC 901, Atom N270 - Chromium on Linux: 14400ms
 
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 339.6ms +/- 1.7%
-----------------------------------------------

ai: 33.5ms +/- 12.7%
astar: 33.5ms +/- 12.7%

audio: 81.9ms +/- 2.6%
beat-detection: 18.4ms +/- 3.8%
dft: 27.9ms +/- 3.9%
fft: 14.1ms +/- 6.5%
oscillator: 21.5ms +/- 1.8%

imaging: 127.5ms +/- 0.5%
gaussian-blur: 48.1ms +/- 0.5%
darkroom: 57.9ms +/- 0.7%
desaturate: 21.5ms +/- 1.8%

json: 19.6ms +/- 2.5%
parse-financial: 8.8ms +/- 3.4%
stringify-tinderbox: 10.8ms +/- 2.8%

stanford: 77.1ms +/- 4.3%
crypto-aes: 19.9ms +/- 2.0%
crypto-ccm: 24.5ms +/- 1.5%
crypto-pbkdf2: 22.9ms +/- 13.4%
crypto-sha256-iterative: 9.8ms +/- 3.1%

14700KF
TUF 4070 OC
MS Edge
Somewhat incredibly, I get this exact score, 339.6, on the same CPU with V8 12.6.0. It makes one wonder if there are quantization problems in Kraken.
 
1TB iPad Pro (M4), iPadOS 17.5
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 319.4ms +/- 3.1%
-----------------------------------------------

ai: 87.1ms +/- 10.5%
astar: 87.1ms +/- 10.5%

audio: 88.5ms +/- 0.9%
beat-detection: 23.2ms +/- 1.3%
dft: 25.2ms +/- 1.8%
fft: 16.0ms +/- 2.1%
oscillator: 24.1ms +/- 1.7%

imaging: 70.3ms +/- 2.1%
gaussian-blur: 24.8ms +/- 1.8%
darkroom: 21.5ms +/- 1.8%
desaturate: 24.0ms +/- 4.2%

json: 13.8ms +/- 3.3%
parse-financial: 6.9ms +/- 3.3%
stringify-tinderbox: 6.9ms +/- 3.3%

stanford: 59.7ms +/- 1.4%
crypto-aes: 18.8ms +/- 2.4%
crypto-ccm: 14.0ms +/- 3.4%
crypto-pbkdf2: 19.0ms +/- 0.0%
crypto-sha256-iterative: 7.9ms +/- 2.9%
 
1TB iPad Pro (M4), iPadOS 17.5
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 319.4ms +/- 3.1%
-----------------------------------------------

ai: 87.1ms +/- 10.5%
astar: 87.1ms +/- 10.5%

audio: 88.5ms +/- 0.9%
beat-detection: 23.2ms +/- 1.3%
dft: 25.2ms +/- 1.8%
fft: 16.0ms +/- 2.1%
oscillator: 24.1ms +/- 1.7%

imaging: 70.3ms +/- 2.1%
gaussian-blur: 24.8ms +/- 1.8%
darkroom: 21.5ms +/- 1.8%
desaturate: 24.0ms +/- 4.2%

json: 13.8ms +/- 3.3%
parse-financial: 6.9ms +/- 3.3%
stringify-tinderbox: 6.9ms +/- 3.3%

stanford: 59.7ms +/- 1.4%
crypto-aes: 18.8ms +/- 2.4%
crypto-ccm: 14.0ms +/- 3.4%
crypto-pbkdf2: 19.0ms +/- 0.0%
crypto-sha256-iterative: 7.9ms +/- 2.9%
These are pretty interesting because they are a mix of way worse and way better than results from an x86 CPU.
 

yd

Ars Legatus Legionis
20,764
Subscriptor++
Looks like its time for an upgrade - this is a 5850x 16 core chip with ddr4 3200mhz ram

===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 559.1ms +/- 1.3%
-----------------------------------------------

ai: 65.7ms +/- 4.9%
astar: 65.7ms +/- 4.9%

audio: 168.8ms +/- 2.0%
beat-detection: 48.5ms +/- 2.3%
dft: 36.7ms +/- 6.1%
fft: 42.8ms +/- 4.8%
oscillator: 40.8ms +/- 5.2%

imaging: 193.2ms +/- 2.1%
gaussian-blur: 62.0ms +/- 4.5%
darkroom: 74.0ms +/- 1.6%
desaturate: 57.2ms +/- 5.1%

json: 28.5ms +/- 7.2%
parse-financial: 14.6ms +/- 13.1%
stringify-tinderbox: 13.9ms +/- 4.5%

stanford: 102.9ms +/- 2.4%
crypto-aes: 28.8ms +/- 3.3%
crypto-ccm: 21.6ms +/- 5.7%
crypto-pbkdf2: 37.2ms +/- 2.2%
crypto-sha256-iterative: 15.3ms +/- 7.6%
 
i9-13900k

===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 335.7ms +/- 0.4%
-----------------------------------------------

ai: 29.4ms +/- 4.2%
astar: 29.4ms +/- 4.2%

audio: 83.4ms +/- 0.8%
beat-detection: 19.2ms +/- 2.4%
dft: 26.9ms +/- 0.8%
fft: 14.4ms +/- 2.6%
oscillator: 22.9ms +/- 1.0%

imaging: 130.8ms +/- 0.3%
gaussian-blur: 48.1ms +/- 0.5%
darkroom: 59.6ms +/- 0.6%
desaturate: 23.1ms +/- 1.8%

json: 17.4ms +/- 2.9%
parse-financial: 7.2ms +/- 4.2%
stringify-tinderbox: 10.2ms +/- 3.0%

stanford: 74.7ms +/- 1.4%
crypto-aes: 19.1ms +/- 2.8%
crypto-ccm: 24.3ms +/- 1.4%
crypto-pbkdf2: 21.8ms +/- 2.1%
crypto-sha256-iterative: 9.5ms +/- 4.0%
 
Looks like its time for an upgrade - this is a 5850x 16 core chip with ddr4 3200mhz ram

===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total: 559.1ms +/- 1.3%
-----------------------------------------------
Maybe a case of change browser or look at the hardware config. My lowly 5600g with 2666 RAM turns in 480 using the current release of Edge on Windows 11.
 

Made in Hurry

Ars Praefectus
4,553
Subscriptor
Something different:

Vivobook 12500H. Version 125.0.6422.141 (Official Build, ungoogled-chromium) (64-bit), Linux Mint 21.3

Code:
===============================================
RESULTS (means and 95% confidence intervals)
-----------------------------------------------
Total:                        462.9ms +/- 0.9%
-----------------------------------------------

  ai:                          38.1ms +/- 1.4%
    astar:                     38.1ms +/- 1.4%

  audio:                      118.4ms +/- 3.7%
    beat-detection:            30.0ms +/- 12.7%
    dft:                       36.2ms +/- 3.7%
    fft:                       21.7ms +/- 1.6%
    oscillator:                30.5ms +/- 1.7%

  imaging:                    172.8ms +/- 0.7%
    gaussian-blur:             63.0ms +/- 1.9%
    darkroom:                  80.2ms +/- 0.4%
    desaturate:                29.6ms +/- 1.7%

  json:                        28.0ms +/- 2.1%
    parse-financial:           13.4ms +/- 2.8%
    stringify-tinderbox:       14.6ms +/- 2.5%

  stanford:                   105.6ms +/- 0.8%
    crypto-aes:                25.8ms +/- 1.8%
    crypto-ccm:                36.2ms +/- 1.6%
    crypto-pbkdf2:             30.2ms +/- 1.0%
    crypto-sha256-iterative:   13.4ms +/- 2.8%