Arion.

Based on your numbers:

MW - 31.72 credits / hour.
EH - 15.50 credits / hour.

However, remember DA wants Seti to be the standard. So how does MW compare to Seti stock, or how does Einstein stock compare to Seti stock? It is possible Einstein is a lower paying project than Seti.

What if we all agree that WCG should be the standard? Will DA get on board and tell SETI to lower their credits to WCG's level? Not. So why do hundreds of thousands of BOINC users have to do whatever DA wants? Shouldn't it be run by committee of elected representatives? Why can't Obama decide? Or me? Or you? I digress...

Using credit per cpu second generally works OK, but it isn't necessarily a true record of what is happening. It doesn't take into account the network bandwidth a project uses, the time spent uploading and downloading WUs, the time spend downloading new application versions (hint, hint, hint), etc. It also makes a difference whether a project is geared towards a specific operating system, processor type, 32bit vs 64 bit, L2 cache, floating point vs. integer calculations, etc. So, just because one machine does double on a project compared to another doesn't mean that it actually earns double the credits per day as another. Go grab some 2-5MB WUs that some projets have and download them over a modem and see how many credits you really get each day. Anyway, looking at a single machine (processor type and features, memory, disk speed, network bandwidth, operating system) does not necessarily represent the stats for all other machines.

For exmaple, ABC grants double the credit per WU for 64 bit machines because they can finish the WU in half the time as a 32 bit machine, and that is while using the STOCK application. Does DA go after ABC to lower their 64 bit credit so that it matches seti? Nope. The 32bit app is the standard. So, I agree with the comment about comparing apples to apples. Stock app to stock app.

Lastly, as far as I'm concerned, alpha and beta projects NEED to have higher credit in order for people to put up with the issues involved in getting them up and running, app errors, system down time, etc. that being said, there should probably be a limit to how long they can remain in alpha or beta status or be pulled from the stats sites.

I'm also wondering how the APP_NAME/APP_VERSION stuff is supposed to work.

right then, this is how I did it

right click on project, select properties, set the configuration box to All configurations,
then Configuration Properties, C/C++, Command Line and added them into the Additional Options box with
/D "APP_NAME=Temujin"
/D "APP_VERSION=0.16"
/D "GMLE_BOINC"

void prob_ok_init() {
	srand48(time(NULL));
}

I don't think you guys have read any of my posts. Unless someone makes a post with a link to their optimized application(s) (preferably in the application code discussion), there's nothing I can do about it.

Speedimic has been nice enough to provide optimized linux apps, and I've stickied the post about them, but no one has been forthcoming for windows.

Also, arguments that we're just trying to keep Dave Anderson happy are probably directed at the wrong person, because he's on my PhD thesis committee :P

Soon there'll be an opt. appl., which will calculate the WU for windows in less than 6 Minutes again.

I known a stock version needs to be the one that runs on any architecture supported by the project but...

A suggestion.
Can you provide real Win x64 application, that has SSE2 enabled?
I mean - right now there is not x64 app (it's a 32-bit fake given to 64-bit hosts) but x64 CPUs are also SSE2 capable.
This way, 64-bit hosts can somehow benefit and provide better performance per watt.

I believe it can be even extened.
It is known what CPU features are available to each host (BOINC client reports what is known to OS) and app can be provided accordingly.
This would mean to have Win stock, Win SSE2, Win SSE3, Win x64 SSE2, Win x64 SSE3 etc and send them to hosts.

Or, you can make a single app that would have all version inside (stock...SSE4.2) and app itself will choose what code version to run.

Could you add something extra in the stock app so that it would be noticed as the true stock.

I have, but the majority of our windows users are not using the stock app.

Sounds like the majority of windows users read the forums. :)

And can anyone confirm what Logan brought up?

@ Travis

Why linux, OSX, and Win stock apps gave different results with the same wu?

If this is the case does that not mean there could be an issue with the stock app too?

There are some issues with the stock app, but this accuracy thing is nothing you can really avoid between different architectures when using standard math libraries. And Travis answer (actually a question) to that problem

At what level of accuracy?

implies he is aware of that.

Actually, this sort of differences in the last bits is what one often calls numerical noise. Both versions are likely to calculate results within the same error bars when compared to a (hypothetical) implementation with infinite (or just somewhat extended) precision.

@ Travis

Why linux, OSX, and Win stock apps gave different results with the same wu?

Whats about girls? Every milion u get one for free, deal?
;D