app_info for AP500, AP503, MB603 and MB608

What is the consequence of dropping the flops entry in app_info?

Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.

What is the consequence of dropping the flops entry in app_info?

Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.

That's what I thought too, and ditto - I deleted the entries as well.

But it seems BOINC downloads way too many WUs for the report deadline, so I don't think it's working the way I'd like.

I will monitor this and furter lower my value for the work cache.

What is the consequence of dropping the flops entry in app_info?

Very little to none. Your initial estimates for time required for tasks will be off, but BOINC figures them out soon enough. They're not very accurate anyway. I quit entering values for flops and platform in app_info.xml quickly. With a mix of machines running 32 and 64 bit operating systems with varying CUDA capability, I found it to be WAY more trouble than it's worth.

That's what I thought too, and ditto - I deleted the entries as well.

But it seems BOINC downloads way too many WUs for the report deadline, so I don't think it's working the way I'd like.

I will monitor this and furter lower my value for the work cache.

Morten

Ok, I have an 8500gt that is estimated at 5 GFLOPS. When I report 6.08s it drags the time to completion of the APs down. So, I should raise the GFLOP in my app_info for the GPU ? Maybe refigure for 6GFLOPs instead of 5?

By the time I've finished an AP V5 I've turned in so many 6.08s the Time to completion guesstimate on the rest of the APs are down to around 12 hours. It really takes me about 60 hours each. Also, when the APs do report it jumps the time for the 6.08s up to around 20 hours and the APs to upwards of 100 hours. I'm sure I did the math right but this is really confusing.

What final flops figures are you using for AP, AP_v5, MB603 and MB608?

Claggy

Why does CPU-Z say I have SSE3 and Boinc says SSE2? Which is the correct I wonder...

The figures you posted are correct, double check your app_info figures,
but i assume you got them from there, so it should't be different,
on my E8500, AP_v5 tends to drive completion times down,
while MB608 eithier drives completion times up or down depending on the AR,
and you're running a VLAR killer, so they won't be driving completion times really high,
Must be something to do with the GPU being very slow, compared to MarkJ's,
I'd try lowering the GPU flops figure first, say 800000000
Put this in a cc_config.xml and monitor what dcf is doing first:

<cc_config>
<log_flags>
<dcf_debug>1</dcf_debug>
</log_flags>
</cc_config>

Claggy

Well you dcf is getting driven down, should end up around 0.2,
you might find particular AR's drive it and completion times back up a bit,
just monitor it for now, let us know what astropulse does,

Claggy

Edit: your CPU time spent feeding the GPU is 4 times what mine is (9800GTX+ on PCI-X 16), i wonder what difference that makes?

....but you'll need to do the cpu flops numbers as I don't have access to your <f_pops> figure.

<p_fpops> (sic) for a Core2 is often very close to the speed in GHz. My E5320 is showing <p_fpops> = 1828798802.551730 - and with a Xeon, there won't be any overclocking to worry about.

Im running an app_info very similar to the one featured in this post. I have upgraded to 6.6.20 in the hope of finally being able to stop micro-managing all my hosts, but Im still having problems with CUDA/AP units. Im running a dual core with a 8800GT and ideally would like the CPU to crunch AP only while the GPU crunches MB units. I have set max_cpu to 3 previously, should I be undoing this in 6.6.20. I am running all the latest optimised apps
I keep getting in from work to find myy host crunching 3 AP units on 2 cores with the GPU idle.
What is the best way to resolve this please?

On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???

http://boincstats.com/stats/boinc_user_graph.php?pr=bo&id=1405036

Thx for the help
____________

I have set max_cpu to 3 previously, should I be undoing this in 6.6.20.


On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???

I have set max_cpu to 3 previously, should I be undoing this in 6.6.20.


On another seperate note, is there a problem with BOINC stats or the berkley databases as I have had a total of 450 approx units credit from SETI???

Definitely get rid of the max_cpus setting. BM 6.6.20 has this function built in.

As for the stats, they are pulled from the replica database which has been down several days for repairs.

Ok..
Cheers for the help, will apply the changes when I get in tonight.
Thanks again
____________