Simple WCG PPD Estimator

[FordGT90Concept]

Ion could download C#.NET Express and make the change himself. XD

Add a line, increment the build number, compile, and upload.


@Ion: You can get rid of my original estimator (wcg_estimator_1_1.zip).

 

[PVTCaboose1337]

Ion could download C#.NET Express and make the change himself. XD

Add a line, increment the build number, compile, and upload.

Yeah [Ion] should do it. That would take a load off us (us meaning you).

 

[[Ion]]

Ion could download C#.NET Express and make the change himself. XD

Add a line, increment the build number, compile, and upload.


@Ion: You can get rid of my original estimator (wcg_estimator_1_1.zip).

Will do in a minute

Yeah [Ion] should do it. That would take a load off us (us meaning you).

I have no objection with that, I'll download it now and start learning how the source code works

 

[PVTCaboose1337]

[Ion] you can remove mine as well if you like, however it is much more refined / pretty than the new combo version, but whatever. Remove yours too or better yet:

USE THIS:

Pretty suite (pun intended) huh?

All our programs, in a rar, might need a readme.

GO HERE: http://forums.techpowerup.com/attachment.php?attachmentid=34801&d=1270768924

 

[FordGT90Concept]

I found a pretty major bug in the benchmark portion of Estimator 2. Ion should get 2.0.1 up soon which fixes it.

The bug: it turns out running the benchmark from Visual Studio is much slower than from Windows. It should theoretically be much more accurate now (it has to do more work to earn each point making estimates more precise).

 

[[Ion]]

[Ion] you can remove mine as well if you like, however it is much more refined / pretty than the new combo version, but whatever. Remove yours too or better yet:

USE THIS:

Pretty suite (pun intended) huh?

All our programs, in a rar, might need a readme.

GO HERE: http://forums.techpowerup.com/attachment.php?attachmentid=34801&d=1270768924

Pardon my stupid, but all I see is a picture, and the link leads to the same pic?

 

[PVTCaboose1337]

Pardon my stupid, but all I see is a picture, and the link leads to the same pic?

Click the link that leads to the picture. Save the picture, rename it as .rar file, open.

 

[FordGT90Concept]

2.0.1 fixes a major bug with benchmarking (the scores were way off). The updated version is on the original post.

 

[FordGT90Concept]

Can someone tell me how accurate the benchmark is compared to the calculator in 2.0.1? Specifically, on an AMD machine and a Core 2 system.

 

[[Ion]]

Can someone tell me how accurate the benchmark is compared to the calculator in 2.0.1? Specifically, on an AMD machine and a Core 2 system.

Sure, just a sec, I'll give it a go on my X4 955 and C2DM P8600

 

[[Ion]]

Sure, just a sec, I'll give it a go on my X4 955 and C2DM P8600

So something is majorly off, the estimator component gives an accurate estimate of ~755 PPD for the C2DM, but the benchmark (set with 100 seconds) gives an estimate of over 25 thousand (BOINC)

On the X4 955, the estimator estimates ~2150 PPD, while the benchmark estimates ~6500 PPD (BOINC)

 

[FordGT90Concept]

That's what I was afraid of.

I might have to automatically detect the processor and adjust accordingly but in order to "adjust accordingly," I have to make an app that estimates the adjustments and people will have to submit that to me so I can put it in the app. That might take a long time to do so in the meantime, the Benchmarking is only accurate on Core i7 (maybe Core i5 aswell) processors.

 

[[Ion]]

That's what I was afraid of.

I might have to automatically detect the processor and adjust accordingly but in order to "adjust accordingly," I have to make an app that estimates the adjustments and people will have to submit that to me so I can put it in the app. That might take a long time to do so in the meantime, the Benchmarking is only accurate on Core i7 (maybe Core i5 aswell) processors.

Well, if there's any experimental data you need, let me know, I'll see what I can do for you

 

[FordGT90Concept]

I found several problems but there are still too many question marks. The attached app will help me fill them in.

It takes about 6 minutes to complete so only do it when you have time. Make sure BOINC/WCG is off before running it or it will invalidate the results.

It will automatically close creating findings.txt in the same directory as the exe when it does. Open that file up and paste the contents here.

 

[[Ion]]

I found several problems but there are still too many question marks. The attached app will help me fill them in.

It takes about 6 minutes to complete so only do it when you have time. Make sure BOINC/WCG is off before running it or it will invalidate the results.

It will automatically close creating findings.txt in the same directory as the exe when it does. Open that file up and paste the contents here.

I'll do this after school today on the C2DM and Phenom II. LMK if you need anything else

 

[[Ion]]

This is long overdue, but if I have enough time this weekend, I'm going to update things with support for all Athlon II models, the Phenom II X6, and the Core i3/i5 Clarkdale...I might also include preliminary support for the i5 (Lynnfield)...unfortunately, I have only limited data to base that off of

 

[FordGT90Concept]

Since the benchmark never got fixed (might never be fix-able), maybe I should remove it and just leave the calculator.

 

[[Ion]]

That sounds good...your choice

If I provide you with the 'numbers' for the new CPUs, could you update it? I don't have Visual Studio or anything installed

 

[[Ion]]

What is this? A new version? Yep

Now with support for the following CPUs:

Intel Core 2 Duo (Conroe)
Intel Core 2 Duo (Wolfdale)
Intel Core 2 Quad (Kentsfield)
Intel Core 2 Quad (Yorkfield)
Intel Core i3/i5 (Clarkdale)
Intel Core i5 (Lynnfield)
Intel Core i7 (quad-core, all types)
Intel Core i7 (hex-core)

AMD Athlon 64X2/Athlon X2
AMD Phenom I X3
AMD Phenom I X4
AMD Athlon II X2
AMD Athlon II X3
AMD Athlon II X4
AMD Phenom II X2
AMD Phenom II X3
AMD Phenom II X4
AMD Phenom II X6


Unfortunately, there are some issues with the latest version as well. It's back to being console-only, something I don't expect I can change any time soon (as this is all I know how to do). Also, it's back to only running on systems with Visual Studio. This I can fix, assuming I have time later, I'm going to address that issue and re-upload it

We're now on to version 0.5.9b, next version will be in the .6.x range.

Any new feature requests for me to start working on?

 

[Chicken Patty]

ION

I'm getting this when I try to open it:

 

[FordGT90Concept]

That sounds good...your choice

If I provide you with the 'numbers' for the new CPUs, could you update it? I don't have Visual Studio or anything installed

Yeah, send it in a PM. I'll get it updated when I can.

ION

I'm getting this when I try to open it:

http://img.techpowerup.org/101025/Capture230.jpg

Try installing this:
Microsoft Visual C++ 2010 Redistributable Package (x86)
Microsoft Visual C++ 2010 Redistributable Package (x64)
Microsoft Visual C++ 2010 Redistributable Package (ia64)

I would try the x86 version because the application is compiled as x86.

 

[Chicken Patty]

Yeah, send it in a PM. I'll get it updated when I can.



Try installing this:
Microsoft Visual C++ 2010 Redistributable Package (x86)
Microsoft Visual C++ 2010 Redistributable Package (x64)
Microsoft Visual C++ 2010 Redistributable Package (ia64)

I would try the x86 version because the application is compiled as x86.

Still get the same error

 

[FordGT90Concept]

Did you try x64 too (assuming you have Windows 64-bit)? I'm not sure which it requires and Microsoft really doesn't say which should be installed.

 

[Chicken Patty]

Did you try x64 too (assuming you have Windows 64-bit)? I'm not sure which it requires and Microsoft really doesn't say which should be installed.

Yep, both!

 

[FordGT90Concept]

It should be in C:\WINDOWS\System32 and C:\WINDOWS\SysWOW64

Installing the redists should have fixed it. Maybe try restarting?


@Ion: This might help fix the error developer-side (statically link the DLL):
http://rhyous.com/2010/09/16/avoiding-the-msvcr100-dll-or-msvcr100d-dll/