Jump to content
HWBOT Community Forums

havli

Members
  • Content Count

    445
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by havli

  1. 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.
  2. Perhaps some Windows tweaks, but that is just a wild guess. I never liked tweaking OS.
  3. 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.
  4. I have no plans to add stress testing. There are plenty of better applications for this.
  5. I don't care what Intel advertise. The important part how the CPU actually runs. And unless your heatsink fall off or something... it will never run at base clock. See here https://www.techpowerup.com/review/intel-core-i9-9900k/17.html Always at 4.4 GHz or more. And depending on the board and bios settings, it might even run 4.8 all-core (with TDP of 200W). Yeah, 50% OC is possible on 9900k - but only with LN2 at >7 GHz. 😉
  6. Nonsense - 9900k never runs at base clock. Default turbo is 4.8 GHz... so OC to 5.1 GHz = +6.25%. This is how it works.
  7. I think it is not that difficult or expensive to get dice pot. But buying the dice itself is rather expensive - last time it cost me $40 for 10 kg. Also it takes a lot of effort to get decent subzero score in general. Most likely because of that not many people are willing to do that... And while water cooling for example is much easier to run, unless you have really golden CPU/GPU you won't get competitive score anyway.
  8. Well, I consider myself retired from overclocking... so I don't really care what is considered server and what isn't. 😄 But as long as you run C2Q or Core i7 in these boards, it should be desktop enough. https://www.asus.com/Motherboards/P5K_WS/ https://www.asus.com/Motherboards/P6T_WS_Professional/overview/
  9. No need to OC PCI when you can run it at 66 MHz in the PCI-X slot. 775 boards with PCI-X definitely exist and I think 1366 too.
  10. You can run PCI GPU in PCI-X board, perhaps it will be somewhat faster.
  11. You mean the elapsed and remaining time? Elapsed time is measured directly by the wrapper, using Java nanoTime() function. And remaining time is prediction based on the amount of frames finished and actual framerate. The x265 encoder executable also measures time (internally, but reports it as fps). However this is the "wall clock time"... so less accurate and vulnerable to system time manipulation. In earlier versions of the benchmark, the score was taken directly from the encoder. But after some cheated scores were discovered I changed the time measuring to use nanoTime() and
  12. @_mat_ At this time I have no plans for future x265 development... Other than perhaps reuploading updated package with recent cpu-z version once in a while, like I did this year after Ryzen 3000 launch. The main executable is more than 1.5 years old and considering I see barely any problems or complains... it means either people don't care 😄 or everything works reasonably well. If you wish to integrate x265 into BenchMate using the DLL injection method, I have no objections. 🙂 However doing new version with native BenchMate integration seems like to much work, especially with testing
  13. Old versions of GPU-Z should work in 2k. For example 0.4.6 worked for me https://hwbot.org/submission/1074470_havli_3dmark2001_se_radeon_7200_ddr_4634_marks
  14. Hint for the X265 4K Dual Core. Perhaps the locked Skylake i3 / Pentium / etc. with BCLK overclocking and disabled AVX might be faster than almost default with AVX2. But who knows...
  15. Updated package with CPU-Z 1.89.1 and newer version of bundled Java is now available. http://hw-museum.cz/data/hwbot/HWBOT_X265_2.2_cpu-z_1.89.1.zip The benchmark itself remains exactly the same, no changes from version 2.2. The new Java might help in some rare cases of application crash when saving the data file. CPU-Z 1.89.1 improves HW detection.
  16. I think this is due to the drivers being older than X299 platform... and thus not allowing to run SLI. Each platform must be white-listed in the driver, otherwise it won't show option to enable SLI. Try this patch https://www.techpowerup.com/forums/threads/sli-with-different-cards.158907/
  17. Very nice and efficient run! My 270X can reach these clocks too... but I doubt I could get anywhere near your score. :D
  18. Not really, it is pain to install W7 on some modern platforms... And for example Raven Ridge is W10 only. In the future this wil get worse and worse.
  19. No, performance should remain the same. The encoding is performed outside of java. The whole benchmark is more or less just a wrapper to x265 encoder.
  20. Thank you for the log file. It seems this might be some kind of a bug in Java. Same problem here for example https://bugs.openjdk.java.net/browse/JDK-8178873 X265 only uses the built-in portable java, should be completely independent on the installed x86 or x64 versions of Java. It even works on systems with no Java installed at all, as a portable benchmark (this was the goal after all). Now the question is how to deal with this issue. One thing that might help could be changing the GUI style to not look like standard Windows application. This would require me to do some changes
  21. @marco.is.not.80 There should be log file next to the executable... HWBOT_x265_Benchmark_log.txt - Does it say anything interesting? The code for manual file saving is unchanged since the beggining (2015 I think) as well as the bundled portable Java. Of course it is possible I did some mistake in there, however it must be very rare set of conditions because in 99.99% cases it works. My bet is something is missing / broken in your OS. Possibly some service or function that is used when saving the file. The benchmark shouldn't just quit like you are experiencing. In ca
  22. Is price of the GPU alone really that important? To get competitive score you must have other equipment (CPU / MB / RAM / LN2 cooling) worth of hundreds $ at very least. So not very cheap anyway.
  23. As for the CPU support - stock PC-DL should be able to run any Prestonia or Gallatin Xeon. Even the 4MB Xeon MP works https://hwbot.org/submission/3520109_havli_superpi___1m_xeon_mp_3.0ghz_33sec_735ms Also it is possible to change CPU voltage (VID) by socket pinmod (similar to socket 462) but is isn't very practical.
  24. ... and the last one can turn off the server and switch the lights off. //edit... but similar analysis of x265 would be interesting of course. On the other hand It holds a risk of finding some kind of a security hole which may not be possible to fix at all... or would take too much of time to be worth it. The fact the benchmark developer is still here doesn't guarantee unlimited maintenance and support.
  25. XTU is one thing... but with enough effort I'm sure many benchmarks can be hacked like this. And I seriously doubt those vulnerabilities will be fixed.
×
×
  • Create New...