Jump to content
HWBOT Community Forums

nick_name

Members
  • Posts

    33
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by nick_name

  1. 1 hour ago, havli said:

    -snip-

    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.

    Is there anything that can be done about the scheduler assigning more resources to one instance over the other?  Or is that by design?  

    In my experiences the gap between the two is usually 40% ~ 45%.  

  2. 1 hour ago, jab383 said:

    I see that big difference between the overkill bars when priority is above NORMAL - in either Win 7 or Win 10.  Try all the priorities and take a peak in task manager during the run to see what actual priority is being used for the workload processes.

    I've played with all the priorities too, but that alone didn't cure it for me.  I did see favorable results combining that while playing with other Windows power plans though.  

     

    What program is it in Task Manager?  Is it Javaw?

  3. 21 minutes ago, _mat_ said:

    In the latest (unreleased) dev versions this is fixed btw. I tested the previously problematic executables with virustotal.com and it didn't trigger a single detection engine, even the ml/dl ones, which are well known for false positives.

    Would an idiot be helpful in the testing?  Someone that has no experience with benchmate at all?  Because I'm that idiot.  

  4. When using Overkill does anyone else see the top or bottom progress bar run away from the other?  I've played with a bunch of different things and it feels like it's a Windows 10 scheduler bug.  Or is that normal behavior?  I've only seen one person bench it on YouTube and I myself only have about a day of experience playing with the benchmark.  

  5. If someone is harnessing the tilt of the earth for their cooling -- is that just submitted as chilled? 

    ie During the winter I install a window fan and then set my pc in front of that for the cold air to be drawn in to the radiators of my AIOs.  Or if someone were to have their rig outside in the cold winter air.  

  6. On 8/1/2020 at 7:34 PM, _mat_ said:

    It's far more complicated than your analogy assumes. Using CINEBENCH on Windows 7 has a completely different timer implementation than running it on Windows 10. By changing OS settings you can additionally change the hardware being used for the meaurement. Actually you don't even need to change anything, Windows might select different time keeping hardware on its own depending on the available platform. And that's alright because benchmarks use WIN32 API functions to measure time and these functions exist to separate application code from platform-dependent code.

    All of the above truly leads to comparing apples and oranges in line with your analogy. The worst part is that we have no data showing time measurement information to understand what is happening behind the scenes.

    Now with BenchMate in control of the benchmark code we can do two things to fix this:

    1) The same time measurement code, logic and hardware is used for all benchmarks.

    2) Add timer statistics to benchmark runs for better analysis

    BenchMate obviously does much more to ensure reliable results. Like using multiple timers to at least triple check the measured time period.

    Of course it is true that there might be differences between BM runs and unprotected runs. The same goes for runs between different systems and OS, so there wasn't any integrity in the first place. But it's never too late to do things the right way.

    Is this why benchmate keeps getting flagged by av software?  And then when I can get it installed av later comes and screws it up?  I tried using it a few months ago, but gave up.  I'm on a team now though and would like to participate when benchmate is required.  

    I'm sorry if this was discussed already.  

×
×
  • Create New...