• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Simple WCG PPD Estimator

OK I lied here is 0.0.4. 0.0.3 failed hard, 0.0.2 was better, 0.0.1 had a bad interface. Still no MHz detection, but I will do in morning (oh shit it is 2am, I mean I will do LATER TODAY!). Users should no longer be able to tell me I have an error cause I fixed them all. Small improvements overall. [Ion] should be quite happy when he awakes. :)

Image improvements as well cut down file size, which is till too big IMO. The NFO page is sadly the biggest...
 

Attachments

Last edited:
PVTCaboose1337 said:
OK I lied here is 0.0.4. 0.0.3 failed hard, 0.0.2 was better, 0.0.1 had a bad interface. Still no MHz detection, but I will do in morning (oh shit it is 2am, I mean I will do LATER TODAY!). Users should no longer be able to tell me I have an error cause I fixed them all. Small improvements overall. [Ion] should be quite happy when he awakes. :)

Image improvements as well cut down file size, which is till too big IMO. The NFO page is sadly the biggest...
Click to expand...

Awesome, thanks a ton! I'll test it out more later and add it to the OP!
 
Great job guys!!!
 
How feasible would a load % line fit into that.. i.e. my 24/7 rig is 100% but my gaming rig runs anywhere from 30 - 80%.
 
AlienIsGOD said:
How feasible would a load % line fit into that.. i.e. my 24/7 rig is 100% but my gaming rig runs anywhere from 30 - 80%.
Click to expand...

I am unsure of the math. My guess is to multiply the PPD by .80 for 80% etc, but I am not sure that is how it works entirely. CPU load is not perfectly linear to being on % of the time methinks.
 
PVTCaboose1337 said:
I am unsure of the math. My guess is to multiply the PPD by .80 for 80% etc, but I am not sure that is how it works entirely. CPU load is not perfectly linear to being on % of the time methinks.
Click to expand...

In BOINC, you can set it to use anywhere from 0 to 100% of the CPU, I think that this is what he is talking about, not how much of the time that it is on. I can easily do this in my console version, just multiply the PPD by the amount of time that it would be on, however, it would be up to you to add this to the VB version
 
[Ion] said:
In BOINC, you can set it to use anywhere from 0 to 100% of the CPU, I think that this is what he is talking about, not how much of the time that it is on. I can easily do this in my console version, just multiply the PPD by the amount of time that it would be on, however, it would be up to you to add this to the VB version
Click to expand...

Adding it now.
 
Here it is.

Capture039416.jpg



Please show me errors guys! You should always see this window if you try and enter anything but an integer.

Capture041.jpg
 

Attachments

Last edited:
you guys are great !! :toast: and yes thats what im talking aboit Ion. Both my rigs crunch 24/7, but my gaming rig is usually at 30% load and set to do work all the time.
 
PVT, I discovered a bug. When you select Phenom II X4 (Deneb), it says "missing or invalid value!" when you hit calculate. Otherwise, everything else works as it should
 
PVTCaboose1337 said:
Please show me errors guys! You should always see this window if you try and enter anything but an integer.
Click to expand...

Good work! This isn't an integer error, but something I stumbled upon none the less:

Once you calculate the PPD for any processor, selecting a different processor from the drop down menu and pressing the calculate button again updates the estimate (very useful).

There is one exception though, whenever you choose Phenom II X4 and press the calculate button it gives the error message, instead of updating the score. Happens on both my machines.

EDIT: Lol [Ion] discoverd it too (I am soo slow at typing)
error.jpg
 
Yeah I fixed it. I thought Deneb was X3 in the code for some reason... it was 2am so...

Also, numerous other improvements added. Going to cut down program size next revision.
 

Attachments

Works great now, thanks!
How do you plan to reduce the size? (I like the NFO, please leave it)

I guess I really need to get some more numbers so that I can get estimates for other types of CPUs (Athlon II primarily, but also Core i5 and Core i3)
 
That picture in the NFO is 41.2kb. It is a PNG. I am going to make it a JPG. Also, if you want anything different in the NFO just PM me.

New version is 38kb. Total. I used a JPG image instead. Looks a little worse, but not much!
 
OMG u guys :rockout:
 
Ok I will upload this, find anymore errors, I will be proud. Size is much improved. Also, auto cpu speed detection will be done when I feel like it.

Capture043.jpg


Image related.
 

Attachments

Last edited:
[Ion] requested an improved error system regarding something like 9000% cpu usage or something. Here is 0.0.8!
 

Attachments

woorks great :respect: :respect: :respect:
 
Excellent, that stops me from selecting over 100% CPU usage. I'll let you know if I have any more ideas/suggestions
 
Hurr made a mistake. Fixed:

CPU speed errors now take precedence over other errors.
 

Attachments

What CPU speed errors do you speak of? I have yet to find any? (even when I enter something like 20,000 for the CPU speed)
 
Clearly I made an error in the speed field, but I made it so the error regarding usage has precedence.

Capture044.jpg
 
i don't know if this supposed to happen but this comes up on 90%- 99%
Capture0082.jpg
 
Last edited:
PVTCaboose1337 said:
Yeah that should not happen... Let me look into it.

EDIT: This is a strange case in my error checking. I will have it fixed ASAP.
Click to expand...

Yep, the same thing is happening for me too, it doesn't seem to depend on the CPU type or speed. But as soon as I enter any CPU usage % between 90 and 99, I get that error.
Still a great app though!
 
You must log in or register to reply here.
Back
Top