Jump to content
HWBOT Community Forums

havli

Members
  • Content Count

    429
  • Joined

  • Last visited

  • Days Won

    3

havli last won the day on October 30 2018

havli had the most liked content!

Community Reputation

77 Excellent

About havli

  • Rank
    robo cop

Converted

  • Location
    CZECH REPUBLIC

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Very nice and efficient run! My 270X can reach these clocks too... but I doubt I could get anywhere near your score. :D
  2. 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.
  3. 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.
  4. 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 in the code, redesign all the graphics objects slightly.... and in the end it would look ugly (IMO ) . Another possibility worth trying is to download updated version of portable Java and replace the old one in X265/Java folder. I have no idea if this can fix the crashing problem or not. On my PC X265 works with both portable java versions (1.8.0_51 and 1.8.0_181)... but I never had this problem. Link for 1.8.0_181 is here: https://www.softpedia.com/get/PORTABLE-SOFTWARE/Programming/Java-Portable.shtml (the x86 version) The direct online submission problem shouldn't be related to this bug, as it doesn't use the file chooser window (which can cause troubles). So this is most likely what _mat_ mentioned.
  5. @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 case something goes wrong, it might just hang or do nothing... however not quit silently. Btw - did you try to redownload the whole benchmark again to make sure some of the files aren't corrupted?
  6. 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.
  7. 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.
  8. ... 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.
  9. 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.
  10. Are PCI VGAs better than AGP for OC? Also I often used PCI SCSI controller because most of the time XP survived moving to completely different platform which doesn't work with IDE. No idea how that can affect OC though.
  11. Ah, yes, that is possible. I almost forgot about Intel OCL driver as it was always slower for me. But is seems lot of people use it with modern CPUs. Anyway for example 9900k can run 100 MHz higher GPUPI 1B than R15, so even with Intel driver it is still rather light benchmark.
  12. Do you have GPUPI 4 for testing? Because I think current versions don't use it, at least not directly... and who knows what instructions is OCL driver using and how much. Also from my experience GPUPI (all public versions available at this time) is actually very light CPU benchmark, at lest on everything I ran it on.
  13. Version 2.44 should be the correct one. Later versions don't work IIRC. I'm not using this bench anymore but from what I can remember - you must submit your score directly, saving the datafile and uploading it later never worked. Also I recall having similar issues of closing the benchmark by itself after the run. Perhaps try to run the bench first and after it is finished login and submit. But it is just a guess.
  14. Well, it is not easy to determine how hard benchmark is. Perhaps I got a little caried away with that statement of R15 and x265 - it seems to be that way on my daily rig, which is bad piece of 8700k. Generally running AVX2 is considered more power demanding but it can be different with each piece of silicon. With mine it can be 10% (as shown above), with yours can be more. Btw - I just did R15 run and it showed 140W... So 140W R15, 145W X265-AVX, 135W X265-nonAVX. So I was't very far off... but probably can't generalize it. Now, I'm sorry, physics and math wasn't my field of study, but let me try to explain why I think this is power consumtion or voltage issue. Semiconductor resistivity drops as temperature rise (unlike normal conductors which are exactly the opposite). So this could create kind of a death spiral. Let's take this model situation: You are running idle, in desktop. Now you start the benchmark (doesn't really matter which one in this example). CPU is fully loaded and temperature rises instantly by few dozen degrees. How much depends on thermal paste mostly. Now thermal capacity of the cooling solution comes to the scene. It is cold at first but slowly starts to heat up. As the cooler heats up, the CPU does too, internal resistivity drops, current increases. Voltage remains the same because hiend OC boards have very strong VRM which can hold the increased current easily. So current increases, temperature increases, power and heat output of the CPU increases..... and this the start of the death spiral. I can't really tell how fast and strong is it but definitely this effect is real and measurable. Most cooling solutions are getting more effective as delta t (the difference between heatsink temperature and the cooling medium temperature) rises. So at some point there will be balance between cooler and CPU. The cooling capability will become strong enough to stop the spiral of increasing temperature / current / heat output... and from this moment the temperature will remain the same. LN2 cooling no doubt is very powerfull but its cooling capability is not infinite. The bigger and heavier LN2 pot you have, the bigger thermal capacity it has. Because of that it will hold the CPU cool for short time because it can absorb the heat. With short benchmarks the block of copper will cover for the few secons long power increase. This is the case of R15. You can run it repeatedly of course but I bet there is always a short break in which pot cools down again and your system is ready for next run. It works like a thermal capacitor. In case of long x265 4k run, thermal capacity of the pot is depleted after a while, and then it will heat up up to the point of balance when boiling LN2 will become strong enough to stop it from getting warmer. Current and temperature rises all the time until the point of balance is reached. Also we shouldn't forget about thermal conductivity of the silicon itself, then thermal paste, then IHS and another layer of thermal paste. More heat the silicon generates, the harder it gets to dissipate it in the LN2 pot (no matter how strong it is) because thermal paste may not be able to conduct the heat well enough. And when you can't get the heat away, then temperature of CPU is rising, current is rising, only this time nothing will stop it... until your system crash. ---------------- I hope you can understand my thoughts. It is difficult to explain when english isn't my native language and my field is IT, not physics.
  15. Even without AVX it is still one of the most CPU intensive benchmarks here on HWBOT. If there is there is a pool in the future and most people would be in favor of non-AVX 4k (or 1080p too?) preset, then of course I can make modified version that will use this option as default. It would be hard to enforce with current version as I believe most people are not familiar with the CPU features override function. Interesting fact - originally it was meant to be used on locked Skylake chips that had very slow AVX when overclocked. So with high enough OC they could be faster without AVX than 103 MHz BCLK with fast AVX. Edit: I also added warning about this problem to x265 description on my website. http://hw-museum.cz/article/1/hwbot-x265-benchmark/1 Noone mentioned any dead AMD CPUs or Intel CPUs when using air or water cooling. Is that correct?
×
×
  • Create New...