havli

Not that it matters for me... but this seems like very lazy fix. Converting the old input format to the new one is very basic math and easy implementation - 10 lines of source code at most. And if users need to convert score to seconds by themselves.... a good way to make them leave.

Any platform older than AM2 or 775 is very unlikely to support HPET. So for pentium 3 version 2.2 is the way to go and IIRC you might need to enable legacy mode too. Link for downloads should be all here http://hw-museum.cz/article/1/hwbot-x265-benchmark/3

I proposed something similar maybe 10 years ago.... nothing happened. So maybe this time.

I tried my best to have correct info on the hw-museum site. Hovewer GPU-Z doesn't detect the NV41/42 core properly. Therefore GF6800 GS is a huge mess here on hwbot.

hw-museum.cz is the homepage of the x265 bench, so all downloads there should be correct. Anything else, I can't guarantee.

Constant, it happened every time on this machine. Also with different GPUs - GTX 670, HD 5870.

Speaking of scores to analyze - this one might help too https://hwbot.org/submission/4939482_havli_aquamark_geforce_gtx_660_oem_466076_marks It was originally detected as regular GTX 660. After I edited it afterwards, I only gives 2 points.

I have similar problem, here https://hwbot.org/submission/4939482_havli_aquamark_geforce_gtx_660_oem_466076_marks The score file is attached. 466076.hwbot

I have new rig for benchmarking old GPUs. i7 8700K @ 5.4 GHz, ASRock Z370 Extreme4 and 2x8 GB DDR4 4100. Now the problem is, I can't get proper 3DM01 scores with this system. Few years ago I had 7700K with Maximus VIII Ranger and the system was somewhat faster despite lower CPU clock and much slower memory. As far as I can tell, the drivers and settings are the same now like I had back in 2017. The winXP install is different, but that canť make the difference or can it? All the CPU limited tests (especially CH, DH, LH) are slower on Z370. So for instance these scores. https://hwbot.org/submission/3527475_havli_3dmark2001_se_radeon_hd_5850_137805_marks https://hwbot.org/submission/4940810_havli_3dmark2001_se_radeon_hd_5870_134006_marks https://hwbot.org/submission/3525093_havli_3dmark2001_se_geforce_gtx_760_(256bit)_142921_marks https://hwbot.org/submission/4938985_havli_3dmark2001_se_geforce_gtx_660_oem_133059_marks All other legacy benchmarks perform better on the 8700k (as expected), but not 01. Is there something I am missing, or simply some boards are for some reason slower and nothing can be done? Thanks for any tips.

I am returning to benchmarking after few years break. Is it allowed to bench two different GPUs - for instance GTX 780 + GTX 780Ti and submit it as 2x GTX 780Ti? I know it was ok in the past... but not sure how is it now. Thanks.

It seems there are some bugs with the new points calculation. For example - I submitted this one just a while ago - it was missdetected as Xeon E5 1607 v3. So I edited to E5 1650 v3 - but now it messed up the ranking and shows 15 points instead of 6... or something like that. https://hwbot.org/submission/4930144_

There is no artificial limit to cores/threads. Perhaps the encoder doesn't scale with so many cores.... it is 4 years old after all.

Perhaps some Windows tweaks, but that is just a wild guess. I never liked tweaking OS.

Javaw.exe is just the benchmark GUI, this one should be left as it is. It has no effect on the performance. When you launch the benchmark run with overkill enabled, then 2 or more instances of the x265 encoder will show up in the device manager and these should have the selected priority set. When running overkill with high(er) priority, the Windows scheduller might assing more system resources to one instance and less to the other - which results in one instance running faster and the other slower. If the score varies too much, then final score won't be valid.

I have no plans to add stress testing. There are plenty of better applications for this.