Realbench v2 [Discussion Thread/Download Links]

[X-ROG]

v2 Leaderboard Link

Download Link (see leaderboard for latest version download)

Offline Upload Link

v2 FAQ

Achievements List

Stress testing and benchmarking insights

[Dr__Zchivago]

So, it looks like I've got the fastest FX-8320, and 11th overall for AMD.
All of you FX-8350 guys had better watch out... I'm coming for you.

Z

Edit: Make that 7th AMD overall.

Edit: 6th AMD

[Dr__Zchivago]

I couldn't help but notice that the Leaderboard lists my CPU clock at ~1500 MHz (which is obviously preposterous). I've made multiple uploads; how can I correct that (or, does it even matter)?

Z

[Ambidexter]

Hi Nodens, MarshallR, HiVizMan,

I love your RB software, thanks to you & Asus for providing it.

What I'm wondering is have you seen some sort of issue where the CPU indication in RB would be "0" while either a bench or stress was running? I was experimenting with changing VCCIO and/or VCCSA, with an eye on increasing stability.(I've encountered a number of different BSOD, freezes, Nvidia crashes, etc. when pushing my OC) As I was testing this, I noticed that the CPU indication in RB would be "0". That happened when the test was going, when the 'puter was idle, and even during both bench and stress testing.

Once I started doing "auto" again, after my testing was done, I noticed the CPU indicator was working again in RB. Could it have been the voltage that caused it, or the executable or DLL was corrupted from my 'puter crashing (and having to rebuild RAID and scan disk for errors)?

Also, as a feature request, I'd like there to be a checkbox on the initial GUI, before starting a bench or stress test, which lets us leave a log entry in an event log. I'd like this as I'd not have to write down when a test started, with what parameters (i.e. duration/memory/stress or bench) so I can see how long it ran before it died or the 'puter BSOD'ed.

It might also be useful if the app would look for this entry in the event log, and report the next time it started "last run was a stress test that requested 8GB memory, and 8 hour duration. It ran for 6 hrs 35 minutes until the system crashed or was reset." (after looking for the proper boot and "system shutdown unexpected" events) If the run was successful and/or produced a score, these could be reported on the next run.

Again thanks for the software!

Cheers,

-Ambi

[Nodens]

Ambidexter wrote:

What I'm wondering is have you seen some sort of issue where the CPU indication in RB would be "0" while either a bench or stress was running? I was experimenting with changing VCCIO and/or VCCSA, with an eye on increasing stability.(I've encountered a number of different BSOD, freezes, Nvidia crashes, etc. when pushing my OC) As I was testing this, I noticed that the CPU indication in RB would be "0". That happened when the test was going, when the 'puter was idle, and even during both bench and stress testing.

Once I started doing "auto" again, after my testing was done, I noticed the CPU indicator was working again in RB. Could it have been the voltage that caused it, or the executable or DLL was corrupted from my 'puter crashing (and having to rebuild RAID and scan disk for errors)?

System instability can cause this. What kind of system instability it's impossible to know unless someone is examining the system with a kernel debugger in real time. And even then that would just narrow it down. It wouldn't pinpoint anything. Use some logic though. If resetting values to auto fixes it then it means there is no corruption of the files and it was induced by the settings.

Also, as a feature request, I'd like there to be a checkbox on the initial GUI, before starting a bench or stress test, which lets us leave a log entry in an event log. I'd like this as I'd not have to write down when a test started, with what parameters (i.e. duration/memory/stress or bench) so I can see how long it ran before it died or the 'puter BSOD'ed.

It might also be useful if the app would look for this entry in the event log, and report the next time it started "last run was a stress test that requested 8GB memory, and 8 hour duration. It ran for 6 hrs 35 minutes until the system crashed or was reset." (after looking for the proper boot and "system shutdown unexpected" events) If the run was successful and/or produced a score, these could be reported on the next run.

Accessing the event log is not a good idea for a multitude of reasons. To list a couple:
a) Implementation is different on each Windows version and would need catering for all.
b) Instability could cause the event log to get corrupted in a way that could be hard to recover.

This could be done with a text file instead in RB's directory BUT instability could also cause this to be corrupted and useless. Also there is no chance of having the granularity you suggest, if you write every second to the file updating it with the current timing value then it's 100% certain that the file would get corrupted on unstable systems making it again useless and possibly creating problems with RB itself because it can not account for every possible way it could get corrupted or parse randomly garbled data.
So in the case of a freeze you can already see the timer on RB. In the case of a stop error, you would get a corrupted file that showed nothing or the last time RB wrote to it. Assuming a 5-10 minute interval you may get something useful as there's less of a chance for a crash to happen during a write but there's still the chance of memory corruption that would cause the file to be written with gibberish multiple times before a crash actually happens so again that defeats the purprose.
So to sum it up. This is a feature that would only be useful in the case of system instability but due to the nature of system instability there's 95% chance that it won't provide any useful data (in case it's a blind write..if there's also reading of the file it can also cause issues). With this in mind it is not worth the time required to implement it.

[Ambidexter]

My thought is really a start record in a log, not necessarily the event log, and a stop record when stopped by hand or upon completion. Showing something on the start page displaying the last few runs or something is just a way to use those data easier than looking in the text file. The "log" checkbox just makes it easier than changing a settings file.

BTW, I think I've fixed my Nvidia driver crashing issue. I relates to upgrades not uninstalling completely and not installing all related software, like 3D, Experience, etc. just graphics and physx drivers. I'll document when testing is finished.

Cheers,

-Ambi

-Ambi

[Dr__Zchivago]

Hey all,

Is the score upload system not currently functioning? Temperatures here finally dipped below freezing last night, and I was able to stretch my CPU's legs; I got some really nice results, and I'd like to upload my scores - but, they're not showing up.

Z

Edit: This is an issue for me, because we don't see sub-zero temperatures in the Texas Gulf Coast very often - haha!

[Arne_Saknussemm]

Well big thanks to Nodens for the OS....ran it and got me a bit more but my encoding and multitasking still way off and couldn't get a king of all badge!

I have a lot to learn still...

😄

[meankeys]

Hay Nodens
Could I trouble you for a copy of your stripped and tweaked ho I mean win 8
Thank You

[Menthol]

meankeys wrote:
Hay Nodens
Could I trouble you for a copy of your stripped and tweaked ho I mean win 8
Thank You

Same here Noden's

[Zoomer360]

Hello!
I have a 7th Place in LeaderBoard http://rog.asus.com/realbench/show_comment.php?id=325
Have a nice Day ^_^ 🙂