Jump to content
HWBOT Community Forums

Morphling

Members
  • Posts

    80
  • Joined

  • Last visited

Posts posted by Morphling

  1. But... the latency of diabolo's score is .2s slower, which seems correct.:P

     

    The bugs are just too hard to spot - we've had situations where we're talking about like 0.4ns - too little to be sure if you ask me. Removing the latency, and have like a combined score of the other 3 tests is an option, but a good solution? I dunno.

     

    Thank you for participating knopflerbruce :)

     

    Ok, you are right :) For me, it would be reasonable to have two solutions:

     

    - Either some latency bugs could be tolerated, when talking about 0.5ns~1ns;

     

    or

     

    - Remove the latency, and have like a combined score of the other 3 tests, as you have said.

     

    But it must be quoted :P

     

    Regards to all

  2. Hm, if the latency bug is the only reason this benchmark isn't rewarded with points, why not let make a hwbot version with latency measured shown but without affecting the final score, so all that counts would be the copy/read/write results?

     

    Hi Hyperhorn, and thanks for participate on this thread.

     

    Well, the point is that the latency is the "soul" of this benchmark. The "secrets" of this benchmark are on how you can make the latency as lower as possible, of course, without bugs.

     

    Without the latency, this benchmark would be resumed to those who could get CPU and RAM as high as possible. That will give your maximum Read/Write/Copy, almost without touching on any other timings.

     

    As I said before, if this would be a quoted benchmark, latency bugs are easily reported.

     

    For example, and I'm sorry for this user, this is a typical latency bug:

     

    http://hwbot.org/submission/2194818_diabolo_80_maxxmem_ddr3_sdram_maxxmem___read_mbytesec._30651

     

    Because when compared to Kintaro's score:

     

    http://hwbot.org/submission/2156559_kintaro_maxxmem_ddr3_sdram_2847.9_marks

     

    We can easily see that Kintaro's settings are much better, and when comparing memory speed and timings, diabolo_80 shouldn't stand chance. He could actualy have at least the same copy/read/write, once he has almost plus 60mhz on the CPU, but never even similar latency. You can see that in my own score:

     

    http://hwbot.org/submission/2208064_morphling_maxxmem_ddr3_sdram_2719.4_marks

     

    I have more mhz on CPU and RAM, but still worse timings, so my latency is beated by Kintaro's settings. It's easy to find these bugs.

     

    Come on, it would be great to have this benchmark to fight.

     

    Regards to all :)

  3. Hi to everyone.

     

    First of all, I must apologize for my bad English. I'm from Portugal, and I'm more or less new here.

     

    I would like to suggest that Maxxmem2 should be quoted for HWBot points. This is an amazing 2D Benchmark, since it doesn't depends only on how much can you give with CPU and RAM, but also lots of RAM tweak and also OS tweaking.

     

    One of the problems that anyone who knows how the benchmark works are the latency bugs. Of course there are lots of people who posts their results with bug, some thinking that it's normal, and others just for cheating.

     

    The point is, if this is a quoted benchmark, then all the users who run this will always pay extreme attention on other users results, making the reports to staff when one of this situations happens.

     

    I think that this is a benchmark that every 2D addicts just love. It's easy to run, and realy hard to make more and more points.

     

    This topic is to have your view point, and also, of course, to try to go further with this :)

     

    Come on, let us have one more 2D benchmark to fight. There are some great overclockers with realy good scores there, like Chew, Kintaro, Billy-the-Kid, MSIMAX, SF3D, slamms, and others that have their scores submited.

     

    Please say what do you all think about this.

     

    Regards to all

     

    Morphling

×
×
  • Create New...