Topic: JRMark -- JRiver's Benchmark Tool (Read 243509 times)

Hendrik · « **Reply #250 on:** September 10, 2014, 02:09:14 am »

The image score is plain CPU image processing, not related to video at all, and it does not use the GPU in the process.

Arindelle · « **Reply #251 on:** September 10, 2014, 02:12:50 am »

Quote from: Hendrik on September 10, 2014, 02:09:14 am

The image score is plain CPU image processing, not related to video at all, and it does not use the GPU in the process.

thanks Hendrik didn't know that. Is their a benchmark for the built-in graphics for the new intel procs ... in relation to MADVr for example?

dean70 · « **Reply #252 on:** September 13, 2014, 10:36:32 pm »

Desktop machine: i5 2500k clocked at 4635Mhz. 16gb ram after cleaning out the dust with 2 fan CPU cooler -

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 2.921 seconds
Single-threaded floating point math... 1.948 seconds
Multi-threaded integer math... 1.468 seconds
Multi-threaded mixed math... 1.022 seconds
Score: 2582

Running 'Image' benchmark...
Image creation / destruction... 0.130 seconds
Flood filling... 0.300 seconds
Direct copying... 0.579 seconds
Small renders... 1.033 seconds
Bilinear rendering... 0.705 seconds
Bicubic rendering... 0.418 seconds
Score: 6951

Running 'Database' benchmark...
Create database... 0.190 seconds
Populate database... 0.859 seconds
Save database... 0.132 seconds
Reload database... 0.036 seconds
Search database... 0.769 seconds
Sort database... 0.732 seconds
Group database... 0.522 seconds
Score: 6636

JRMark (version 20.0.14): 5390

6233638 · « **Reply #253 on:** September 14, 2014, 06:12:05 am »

Quote from: dean70 on September 13, 2014, 10:36:32 pm

Desktop machine: i5 2500k clocked at 4635Mhz. 16gb ram
JRMark (version 20.0.14): 5390

Are you using particularly fast RAM?
I'm unable to break 5K at 4.7GHz on my system (also a 2500K) - that scored 4948.

syndromeofadown · « **Reply #254 on:** September 14, 2014, 12:35:34 pm »

Quote

Are you using particularly fast RAM?
I'm unable to break 5K at 4.7GHz on my system - that scored 4948.

Are you using a SSD and GPU?

My score is over 5K at 3.5GHZ on my computer.
I have 2X4GB DDR3-2133.

6233638 · « **Reply #255 on:** September 14, 2014, 01:39:36 pm »

Quote from: syndromeofadown on September 14, 2014, 12:35:34 pm

Are you using a SSD and GPU?

It's a CPU test so those should not be relevant. I am running one of the newer SATA3 Sandisk Enterprise SSDs though, and have a GTX570.

Quote from: syndromeofadown on September 14, 2014, 12:35:34 pm

My score is over 5K at 3.5GHZ on my computer.
I have 2X4GB DDR3-2133.

Well I'd expect that from a 4770K. (which may be turboing to 3.9GHz)
I should have made it clearer (now edited) that I have the same CPU as dean70, yet he's scoring quite a bit higher than I did, at lower clockspeeds.

I'm running 8-8-8-24, 1600MHz RAM, and was wondering if he was using anything faster. (but higher latency)
Generally most testing I've seen suggested that there's barely any difference from RAM speeds beyond 1600MHz on Sandy Bridge, and indicated that latency was the bigger issue, but >10% seems significant.

dean70 · « **Reply #256 on:** September 14, 2014, 04:27:26 pm »

Quote from: 6233638 on September 14, 2014, 06:12:05 am

Are you using particularly fast RAM?
I'm unable to break 5K at 4.7GHz on my system (also a 2500K) - that scored 4948.

Running 1600 ram (9-9-9-24), but have the BClk running at 103 with 45 mulitpler. It doesnt like mult > 45 - will bluescreen or hang, even though it might get through Prime95 tests.

6233638 · « **Reply #257 on:** September 14, 2014, 05:08:57 pm »

Quote from: dean70 on September 14, 2014, 04:27:26 pm

Running 1600 ram (9-9-9-24), but have the BClk running at 103 with 45 mulitpler. It doesnt like mult > 45 - will bluescreen or hang, even though it might get through Prime95 tests.

Very strange. I didn't think BCLK did much for the system, and I'd expect that would only get you an extra 3% not nearly as much as that.
What OS are you running? I'm on 8.1

glynor · « **Reply #258 on:** September 14, 2014, 06:40:20 pm »

Quote from: 6233638 on September 14, 2014, 01:39:36 pm

It's a CPU test so those should not be relevant. I am running one of the newer SATA3 Sandisk Enterprise SSDs though, and have a GTX570.

It isn't just a CPU test. It replicates MC behavior. The Database tests in particular improved by a fair margin on my machine when I just switched an existing machine to a SSD.

I think some of the image tests are streamed from disk as well, as MC does it, so they might be impacted as well (though I don't remember so clearly here, and some of them are blitting to the screen tests).

dean70 · « **Reply #259 on:** September 14, 2014, 07:10:59 pm »

Quote from: 6233638 on September 14, 2014, 05:08:57 pm

Very strange. I didn't think BCLK did much for the system, and I'd expect that would only get you an extra 3% not nearly as much as that.
What OS are you running? I'm on 8.1

Running Windows 7. M/B is an Asus P8P67.

adlelare · « **Reply #260 on:** September 23, 2014, 08:39:05 am »

where in JRiver do i find JRMark??? TIA

Arindelle · « **Reply #261 on:** September 23, 2014, 08:55:33 am »

Quote from: adlelare on September 23, 2014, 08:39:05 am

where in JRiver do i find JRMark??? TIA

under the Help menu

bob · « **Reply #262 on:** October 20, 2014, 12:54:25 pm »

RPi model B 900 mhz

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
   Single-threaded integer math... 44.722 seconds
   Single-threaded floating point math... 66.916 seconds
   Multi-threaded integer math... 47.113 seconds
   Multi-threaded mixed math... 69.287 seconds
Score: 83

Running 'Image' benchmark...
   Image creation / destruction... 20.737 seconds
   Flood filling... 43.618 seconds
   Direct copying... 21.999 seconds
   Small renders... 12.870 seconds
   Bilinear rendering... 34.232 seconds
   Bicubic rendering... 11.387 seconds
Score: 152

Running 'Database' benchmark...
   Create database... 57.738 seconds
   Populate database... 130.762 seconds
   Save database... 8.187 seconds
   Reload database... 3.228 seconds
   Search database... 106.427 seconds
   Sort database... 54.265 seconds
   Group database... 58.455 seconds
Score: 51

JRMark (version 20.0.26): 96

JimH · « **Reply #263 on:** October 20, 2014, 01:12:27 pm »

Quote from: bob on October 20, 2014, 12:54:25 pm

RPi model B 900 mhz

=== Running Benchmarks (please do not interrupt) ===

JRMark (version 20.0.26): 96

No way! The pi runs MC?

Hendrik · « **Reply #264 on:** October 20, 2014, 01:37:49 pm »

You should really give Bob a decent tiny ARM device, the Pi's are just hilariously slow (even for their price).

6233638 · « **Reply #265 on:** October 20, 2014, 01:45:38 pm »

Quote from: Hendrik on October 20, 2014, 01:37:49 pm

You should really give Bob a decent tiny ARM device, the Pi's are just hilariously slow (even for their price).

Something like NVIDIA's Jetson TK1 looks pretty nice, and seems like it would be able to handle anything you throw at it if you wanted to port over something like Theater View too.

bob · « **Reply #266 on:** October 20, 2014, 01:49:44 pm »

Quote from: JimH on October 20, 2014, 01:12:27 pm

No way! The pi runs MC?

Sigh,
I was kinda hoping no one would notice...

bob · « **Reply #267 on:** October 20, 2014, 01:57:18 pm »

Any dev platform would need to run vanilla debian wheezy like the Pi.

JimH · « **Reply #268 on:** October 20, 2014, 02:01:43 pm »

Quote from: bob on October 20, 2014, 01:49:44 pm

Sigh,
I was kinda hoping no one would notice...

Sure.

JimH · « **Reply #269 on:** October 20, 2014, 02:03:41 pm »

Quote from: Hendrik on October 20, 2014, 01:37:49 pm

You should really give Bob a decent tiny ARM device, the Pi's are just hilariously slow (even for their price).

Bob does his best work on hardware that is hopelessly out of date. It's his way and we all admire him for it.

mojave · « **Reply #270 on:** October 20, 2014, 02:10:31 pm »

Quote from: bob on October 20, 2014, 12:54:25 pm

JRMark (version 20.0.26): 96

Looks like a baseball stat: Royals post season innings (80) plus total home runs in those post season games (16)

bob · « **Reply #271 on:** October 20, 2014, 02:11:13 pm »

Quote from: mojave on October 20, 2014, 02:10:31 pm

Looks like a baseball stat: Royals post season innings (80) plus total home runs in those post season games (16)

Ought to be a good WS!

Hendrik · « **Reply #272 on:** October 20, 2014, 02:37:01 pm »

Quote from: 6233638 on October 20, 2014, 01:45:38 pm

Something like NVIDIA's Jetson TK1 looks pretty nice, and seems like it would be able to handle anything you throw at it if you wanted to port over something like Theater View too.

Those things are pretty expensive though.
There is a middleground in something like the ODROID U3. Samsung Galaxy S3 performance for $65

mwillems · « **Reply #273 on:** November 03, 2014, 07:35:29 pm »

Just built a new system (i7-4790K slightly overclocked (turbo to 4.6 instead of the 4.4 stock), with 16 GB of 2400 MHz GSkill Trident ram, and a Samsung 840 Pro SSD; using integrated graphics for now):

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
   Single-threaded integer math... 3.146 seconds
   Single-threaded floating point math... 1.931 seconds
   Multi-threaded integer math... 1.060 seconds
   Multi-threaded mixed math... 0.611 seconds
Score: 2816

Running 'Image' benchmark...
   Image creation / destruction... 0.273 seconds
   Flood filling... 0.376 seconds
   Direct copying... 0.547 seconds
   Small renders... 0.870 seconds
   Bilinear rendering... 0.641 seconds
   Bicubic rendering... 0.382 seconds
Score: 7122

Running 'Database' benchmark...
   Create database... 0.145 seconds
   Populate database... 0.858 seconds
   Save database... 0.215 seconds
   Reload database... 0.041 seconds
   Search database... 0.662 seconds
   Sort database... 0.556 seconds
   Group database... 0.440 seconds
Score: 7368

JRMark (version 20.0.30): 5769

Still tuning; these settings are Prime95 stable. The JRMark delta between stock and the overclock was about 200 points, so I might be able to squeak another hundred or two out. I don't think I'll be able to break 6k on a stable overclock though [EDIT: Managed to push it to 5970 with a stable overclock, but I can't go any higher without instability].

Still quite happy

Arindelle · « **Reply #274 on:** November 04, 2014, 02:59:00 am »

question is it helpful to list all benchmarks here? or are you interested in just very fast, very slow, or strange hardware here.

Just saying as I brought 6 friends into JRiver and can post their setups if this helps

JimH · « **Reply #275 on:** November 04, 2014, 04:44:30 am »

This is just a show me yours and I'll show you mine thread. It has no particular purpose. It may be useful to people who don't know whether they have a fast or a slow machine.

Arindelle · « **Reply #276 on:** November 04, 2014, 11:55:55 am »

ok. thanks Jim

Anodyne · « **Reply #277 on:** November 04, 2014, 08:12:06 pm »

Intel 4770K @4.5GHz: 6047

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 3.325 seconds
Single-threaded floating point math... 2.032 seconds
Multi-threaded integer math... 1.085 seconds
Multi-threaded mixed math... 0.575 seconds
Score: 2708

Running 'Image' benchmark...
Image creation / destruction... 0.270 seconds
Flood filling... 0.275 seconds
Direct copying... 0.311 seconds
Small renders... 0.915 seconds
Bilinear rendering... 0.680 seconds
Bicubic rendering... 0.396 seconds
Score: 7728

Running 'Database' benchmark...
Create database... 0.155 seconds
Populate database... 0.745 seconds
Save database... 0.095 seconds
Reload database... 0.028 seconds
Search database... 0.683 seconds
Sort database... 0.584 seconds
Group database... 0.500 seconds
Score: 7706

JRMark (version 20.0.30): 6047

bob · « **Reply #278 on:** February 06, 2015, 11:45:12 am »

Cubox-i

588

mwillems · « **Reply #279 on:** February 10, 2015, 07:39:54 am »

ODROID U3: http://www.hardkernel.com/main/products/prdt_info.php?g_code=g138745696275
(but see ARM thread for some caveats: http://yabb.jriver.com/interact/index.php?topic=95459.msg657618#msg657618)

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
   Single-threaded integer math... 5.882 seconds
   Single-threaded floating point math... 10.583 seconds
   Multi-threaded integer math... 2.979 seconds
   Multi-threaded mixed math... 5.369 seconds
Score: 766

Running 'Image' benchmark...
   Image creation / destruction... 2.549 seconds
   Flood filling... 2.732 seconds
   Direct copying... 3.754 seconds
   Small renders... 1.728 seconds
   Bilinear rendering... 1.843 seconds
   Bicubic rendering... 0.449 seconds
Score: 1685

Running 'Database' benchmark...
   Create database... 2.873 seconds
   Populate database... 8.043 seconds
   Save database... 1.065 seconds
   Reload database... 0.495 seconds
   Search database... 6.366 seconds
   Sort database... 4.431 seconds
   Group database... 2.781 seconds
Score: 825

JRMark (version 20.0.66): 1092

mwillems · « **Reply #280 on:** February 10, 2015, 07:41:26 am »

ODROID C1: http://www.hardkernel.com/main/products/prdt_info.php
but see the ARM thread for significant issues: http://yabb.jriver.com/interact/index.php?topic=95459.msg657626#msg657626

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
   Single-threaded integer math... 9.140 seconds
   Single-threaded floating point math... 14.030 seconds
   Multi-threaded integer math... 4.736 seconds
   Multi-threaded mixed math... 7.228 seconds
Score: 541

Running 'Image' benchmark...
   Image creation / destruction... 2.551 seconds
   Flood filling... 4.568 seconds
   Direct copying... 5.207 seconds
   Small renders... 2.345 seconds
   Bilinear rendering... 2.629 seconds
   Bicubic rendering... 0.560 seconds
Score: 1232

Running 'Database' benchmark...
   Create database... 4.151 seconds
   Populate database... 11.856 seconds
   Save database... 1.251 seconds
   Reload database... 0.474 seconds
   Search database... 10.795 seconds
   Sort database... 8.607 seconds
   Group database... 5.162 seconds
Score: 508

JRMark (version 20.0.66): 760

mwillems · « **Reply #281 on:** February 13, 2015, 09:31:51 pm »

Raspberry Pi version 2, overclocked using the built in overclocking option (1000MHz):

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 11.084 seconds
Single-threaded floating point math... 21.667 seconds
Multi-threaded integer math... 5.737 seconds
Multi-threaded mixed math... 11.291 seconds
Score: 382

Running 'Image' benchmark...
Image creation / destruction... 3.275 seconds
Flood filling... 5.884 seconds
Direct copying... 6.866 seconds
Small renders... 3.113 seconds
Bilinear rendering... 3.551 seconds
Bicubic rendering... 0.946 seconds
Score: 931

Running 'Database' benchmark...
Create database... 6.012 seconds
Populate database... 16.344 seconds
Save database... 1.756 seconds
Reload database... 0.625 seconds
Search database... 15.081 seconds
Sort database... 10.450 seconds
Group database... 7.052 seconds
Score: 375

JRMark (version 20.0.66): 563

6233638 · « **Reply #282 on:** February 14, 2015, 02:01:30 am »

Quite an improvement over the model B's score of 96!

Seems like that would handle just about anything you ask of it as far as audio is concerned, other than DSD→PCM or DST-compressed DSD.

mwillems · « **Reply #283 on:** February 14, 2015, 06:02:54 am »

Quote from: 6233638 on February 14, 2015, 02:01:30 am

Quite an improvement over the model B's score of 96!

Seems like that would handle just about anything you ask of it as far as audio is concerned, other than DSD→PCM or DST-compressed DSD.

Check out my review in the ARM thread: yabb.jriver.com/interact/index.php?topic=95459.0

Without derailing too much, it seems to play audio very well and can even handle light audio transcoding (FLAC to mp3 for gizmo).
. I didn't try DSD because I have no DSD files or DSD-capable equipment.

FWIW, the original Pi B+ could handle basic audio duties albeit with quite a bit of UI lag (and definitely no transcoding) provided you similarly overclocked it (see the ARM thread for more details).

thane108 · « **Reply #284 on:** March 20, 2015, 09:29:56 am »

Did a benchmark on my new build - boy have computers evolved since the first benchmarks were posted.

I'm running an I5-4690k and an asus 970 strix (that I haven't overclocked yet).

JMark score is 5336

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 3.566 seconds
Single-threaded floating point math... 2.178 seconds
Multi-threaded integer math... 2.079 seconds
Multi-threaded mixed math... 1.140 seconds
Score: 2120

Running 'Image' benchmark...
Image creation / destruction... 0.283 seconds
Flood filling... 0.297 seconds
Direct copying... 0.437 seconds
Small renders... 0.978 seconds
Bilinear rendering... 0.709 seconds
Bicubic rendering... 0.403 seconds
Score: 7082

Running 'Database' benchmark...
Create database... 0.168 seconds
Populate database... 0.834 seconds
Save database... 0.142 seconds
Reload database... 0.049 seconds
Search database... 0.766 seconds
Sort database... 0.647 seconds
Group database... 0.553 seconds
Score: 6807

JRMark (version 20.0.63): 5336

xprettylightsx · « **Reply #285 on:** April 03, 2015, 11:47:10 am »

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 5.025 seconds
Single-threaded floating point math... 2.962 seconds
Multi-threaded integer math... 2.725 seconds
Multi-threaded mixed math... 1.821 seconds
Score: 1516

Running 'Image' benchmark...
Image creation / destruction... 0.379 seconds
Flood filling... 0.420 seconds
Direct copying... 0.602 seconds
Small renders... 1.331 seconds
Bilinear rendering... 1.687 seconds
Bicubic rendering... 1.063 seconds
Score: 4013

Running 'Database' benchmark...
Create database... 0.229 seconds
Populate database... 1.845 seconds
Save database... 0.934 seconds
Reload database... 0.203 seconds
Search database... 1.076 seconds
Sort database... 2.386 seconds
Group database... 1.376 seconds
Score: 2671

JRMark (version 20.0.87): 2733

sstyle · « **Reply #286 on:** May 12, 2015, 06:23:19 am »

Asus EEEPC 901:

=== Измерение Производительности (пожалуйста, не прерывайте) ===

Запущен 'Математический' Тест...
Однопоточное вычисление, целочисленное... 21.578 секунды
Однопоточное вычисление, с плавающей точкой... 10.160 секунды
Многопоточное вычисление, целочисленное... 24.031 секунды
Многопоточное вычисление, смешанное... 10.818 секунды
Score: 285

Запущен 'Изображение' Тест...
Изображение создание / уничтожение... 1.712 секунды
Заполнение... 2.485 секунды
Прямое копирование... 5.208 секунды
Малая отрисовка... 11.374 секунды
Билинейная отрисовка... 15.134 секунды
Бикубическая отрисовка... 12.071 секунды
Score: 458

Запущен 'База данных' Тест...
Создание базы данных... 5.510 секунды
Заполнение базы данных... 9.277 секунды
Сохранение базы данных... 1.295 секунды
Перезагрузка базы данных... 0.415 секунды
Поиск в базе данных... 8.395 секунды
Сортировка базы данных... 6.814 секунды
Группировка в базе данных... 5.272 секунды
Score: 581

JRMark (version 20.0.63): 442

skanet · « **Reply #287 on:** August 17, 2015, 12:51:20 pm »

=== Esecuzione Benchmark (si prega di non interrompere) ===

Esecuzione 'Matematico' benchmark...
Singolo-comando intero matematico... 3,806 secondi
Singolo-comando punto mobile matematico... 2,341 secondi
Multi comando intero matematico... 1,228 secondi
Multi comando misto matematico... 0,780 secondi
Score: 2330

Esecuzione 'Immagine' benchmark...
Creazione / Distruzione Immagine... 0,245 secondi
Riempimento... 0,313 secondi
Copia diretta... 0,415 secondi
Render piccoli... 1,052 secondi
Rendering bilineare... 0,778 secondi
Rendering bicubic... 0,446 secondi
Score: 6775

Esecuzione 'Database' benchmark...
Crea database... 0,255 secondi
Popola il database... 0,878 secondi
Salva database... 0,138 secondi
Ricarica database... 0,044 secondi
Cerca database... 0,785 secondi
Ordina database... 0,920 secondi
Raggruppa database... 0,536 secondi
Score: 6046

JRMark (version 20.0.103): 5050

JimH · « **Reply #288 on:** August 17, 2015, 01:00:45 pm »

Very good.

BradATIMA · « **Reply #289 on:** August 17, 2015, 04:25:36 pm »

NUC Model : D54250WYKH
Running Window 10 64-bit

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 5.817 seconds
Single-threaded floating point math... 3.563 seconds
Multi-threaded integer math... 3.545 seconds
Multi-threaded mixed math... 2.128 seconds
Score: 1262

Running 'Image' benchmark...
Image creation / destruction... 0.546 seconds
Flood filling... 0.476 seconds
Direct copying... 0.578 seconds
Small renders... 1.585 seconds
Bilinear rendering... 2.040 seconds
Bicubic rendering... 1.285 seconds
Score: 3378

Running 'Database' benchmark...
Create database... 0.281 seconds
Populate database... 1.601 seconds
Save database... 0.422 seconds
Reload database... 0.079 seconds
Search database... 1.265 seconds
Sort database... 1.409 seconds
Group database... 0.993 seconds
Score: 3553

JRMark (version 21.0.2): 2731

emmett82 · « **Reply #290 on:** August 22, 2015, 06:41:15 am »

so far i realllly love this programs it does all my media needs and then some. here is my bench mark to compare

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
   Single-threaded integer math... 3.748 seconds
   Single-threaded floating point math... 2.317 seconds
   Multi-threaded integer math... 1.180 seconds
   Multi-threaded mixed math... 0.801 seconds
Score: 2362

Running 'Image' benchmark...
   Image creation / destruction... 0.319 seconds
   Flood filling... 0.311 seconds
   Direct copying... 0.377 seconds
   Small renders... 1.057 seconds
   Bilinear rendering... 0.783 seconds
   Bicubic rendering... 0.446 seconds
Score: 6682

Running 'Database' benchmark...
   Create database... 0.181 seconds
   Populate database... 0.921 seconds
   Save database... 0.187 seconds
   Reload database... 0.049 seconds
   Search database... 0.773 seconds
   Sort database... 0.907 seconds
   Group database... 0.561 seconds
Score: 6007

JRMark (version 20.0.131): 5017

i wonder if i could improve this score some how

JimH · « **Reply #291 on:** August 22, 2015, 09:37:32 am »

You could over clock a little. Ask on our hardware board.

emmett82 · « **Reply #292 on:** August 22, 2015, 03:03:45 pm »

Quote from: JimH on August 22, 2015, 09:37:32 am

You could over clock a little. Ask on our hardware board.

good idea but ummm i already did right now im setting at 4.6 ghz on the cpu and 1.5 on the gpu. my sound card does not have a official windows 10 driver (YET) so that might help increase the score when i can get it

st1 · « **Reply #293 on:** August 28, 2015, 01:58:13 pm »

intel NUC i7RYH
- ubuntu 14.04 64bit & JRiver 21

math: 1869
image: 1744
db: 5862
JRMark (version 21.0.4): 3158

edit ubuntu 16.04
Running 'Math' benchmark... Score: 1759
Running 'Image' benchmark... Score: 3813
Running 'Database' benchmark.. Score: 4646

JRMark (version 21.0.88): 3406

kamimeguro · « **Reply #294 on:** October 03, 2015, 06:40:40 pm »

New PC > 4690K, 16 G, W10/64

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 3.343 seconds
Single-threaded floating point math... 2.061 seconds
Multi-threaded integer math... 1.058 seconds
Multi-threaded mixed math... 0.689 seconds
Score: 2657

Running 'Image' benchmark...
Image creation / destruction... 0.307 seconds
Flood filling... 0.297 seconds
Direct copying... 0.467 seconds
Small renders... 0.939 seconds
Bilinear rendering... 0.848 seconds
Bicubic rendering... 0.493 seconds
Score: 6567

Running 'Database' benchmark...
Create database... 0.161 seconds
Populate database... 0.968 seconds
Save database... 0.335 seconds
Reload database... 0.081 seconds
Search database... 0.725 seconds
Sort database... 0.834 seconds
Group database... 0.564 seconds
Score: 5862

JRMark (version 21.0.11): 5029

shelby1420 · « **Reply #295 on:** November 11, 2015, 09:43:20 am »

New laptop score..... is it enough?

= Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
Single-threaded integer math... 3.808 seconds
Single-threaded floating point math... 4.266 seconds
Multi-threaded integer math... 2.331 seconds
Multi-threaded mixed math... 2.562 seconds
Score: 1465

Running 'Image' benchmark...
Image creation / destruction... 1.019 seconds
Flood filling... 1.283 seconds
Direct copying... 1.792 seconds
Small renders... 2.149 seconds
Bilinear rendering... 2.050 seconds
Bicubic rendering... 1.710 seconds
Score: 2199

Running 'Database' benchmark...
Create database... 0.465 seconds
Populate database... 2.915 seconds
Save database... 0.897 seconds
Reload database... 0.263 seconds
Search database... 1.986 seconds
Sort database... 1.983 seconds
Group database... 1.123 seconds
Score: 2232

JRMark (version 21.0.19): 1965

InflatableMouse · « **Reply #296 on:** January 02, 2016, 05:41:05 am »

On Linux, latest version 21.0.28:

Code: [Select]

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
    Single-threaded integer math... 3.316 seconds
    Single-threaded floating point math... 2.285 seconds
    Multi-threaded integer math... 1.680 seconds
    Multi-threaded mixed math... 1.164 seconds
Score: 2250

Running 'Image' benchmark...
    Image creation / destruction... 3.295 seconds
    Flood filling... 0.217 seconds
    Direct copying... 0.355 seconds
    Small renders... 0.732 seconds
    Bilinear rendering... 0.583 seconds
    Bicubic rendering... 0.303 seconds
Score: 4011

Running 'Database' benchmark...
    Create database... 0.228 seconds
    Populate database... 0.901 seconds
    Save database... 0.199 seconds
    Reload database... 0.102 seconds
    Search database... 0.594 seconds
    Sort database... 0.671 seconds
    Group database... 0.432 seconds
Score: 6876

JRMark (version 21.0.28): 4379

I'll switch to windows on this same machine and run it again.

Holy crap that's a big difference:

Code: [Select]

=== Running Benchmarks (please do not interrupt) ===

Running 'Math' benchmark...
    Single-threaded integer math... 3,321 seconds
    Single-threaded floating point math... 2,284 seconds
    Multi-threaded integer math... 1,933 seconds
    Multi-threaded mixed math... 1,165 seconds
Score: 2183

Running 'Image' benchmark...
    Image creation / destruction... 0,260 seconds
    Flood filling... 0,219 seconds
    Direct copying... 0,339 seconds
    Small renders... 0,809 seconds
    Bilinear rendering... 0,605 seconds
    Bicubic rendering... 0,333 seconds
Score: 8573

Running 'Database' benchmark...
    Create database... 0,139 seconds
    Populate database... 0,863 seconds
    Save database... 0,258 seconds
    Reload database... 0,073 seconds
    Search database... 0,650 seconds
    Sort database... 0,728 seconds
    Group database... 0,491 seconds
Score: 6714

JRMark (version 21.0.30): 5823

blgentry · « **Reply #297 on:** January 02, 2016, 08:20:55 am »

Image creation/destruction is practically the entire difference (in this case) between Linux and Windows benchmark results. I wonder why that is?

Brian.

InflatableMouse · « **Reply #298 on:** January 02, 2016, 08:51:46 am »

Yeah, not sure.

Video driver perhaps? Not sure if it uses GPU/hardware accelleration or not. If it uses software rendering on Linux that might explain it?

haylo75 · « **Reply #299 on:** January 05, 2016, 09:49:23 am »

Wow, the Linux vs. Windows Image benchmark differential does deserve some investigation / explanation. I was perusing through here as I contemplate a new HTPC build, and that alone makes me ponder Linux.

INTERACT FORUM

Author Topic: JRMark -- JRiver's Benchmark Tool (Read 243509 times)