We are having problems with the Windows application which seems to fail on a certain type of workunits.
So, we have also delayed the Linux application to let them out together. Probably by the weekend.

Sorry for the delay.

gdf

Thanks for the update. Will this version reduce the Windows cpu usage?

No, it will just increase process priority as in this version there are already enough other changes.
If all works, the reduced cpu version will follow in two days.

gdf

No, it will just increase process priority as in this version there are already enough other changes.
If all works, the reduced cpu version will follow in two days.

gdf

That's certainly fine, thanks.

If all works, the reduced cpu version will follow in two days.

Yes, this is what I'm waiting for.
I hope it will be much better than the current one, it's a mess on a slow card like mine. ;-)

---

Member of BOINC@Heidelberg and ATA!

If all works, the reduced cpu version will follow in two days.

Yes, this is what I'm waiting for.
I hope it will be much better than the current one, it's a mess on a slow card like mine. ;-)

WOn't change a ting for the slow cards ...

It will only reduce the laod on the CPU allowing more production towards CPU intense projects if you are tunning them.

So, for example, my productivity on the i7 and quad should rise some because I run n+1 and with the extra load on the processor supporting GPU grid I "lose" some capacity for other projects ...

---

I think DrNow means that the high cpu load especially hurts on his slow card, as the "well, you're getting enough credits from your GPU to compensate" doesn't work as well as with e.g. a GTX 260.

MrS

---

Scanning for our furry friends since Jan 2002

WOn't change a ting for the slow cards ...

You would wonder...
Having a 9600GT on an X2 and the same time an app with high CPU load reduces the capability to crunch on other WUs a lot!
I give you some examples from my WU-list:
This was the last one with app 6.45 and look at the CPU-load, not even 5 minutes!!!
With this app I made the most credits because with the 2+1 setting the GPU almost crunched on it's own, it worked bravely. :-)
6.48 already made the CPU-load higher and it recuded the crunching overall massively for me, the setting 2+1 didn't worked that good anymore, was the same like not to use it.
The CPU-load with 6.52 was better, but still too high.
And with 6.55 it didn't changed that much, but due to my problem with the "unspecified launch failure" I had to recude the clock rate and I guess, this influences the CPU-load as well a bit.
Only positive thing with the higher CPU-load I see in the GPU temperature, it isn't that high as earlier anymore.
I'm thrilled how the new app will work... ;-)

---

Member of BOINC@Heidelberg and ATA!

Yesterday I made my first WU aplication version 6.60 and it made less use of the GPU (the temperature is 7º lower than the same GPU processing a v.6.55 WU) and the points per hour generated were ~380 while with the v6.55 there are ~550 (so with older WUs I get ~50% more points).

Hmmm... Still get a 6.55 WU...

only get the 6.55 too

only get the 6.55 too

I don't think it is a released application. Which is a shame as I am eagerly awaiting the upgrade so that I can get higher GPU production on my other projects. The shame of it for me is that the GPU Grid connected machines are my number 1 and 3 producers ...

But, I can wait ... I guess ... sigh ... :)

---

I'm now crunching my second v6.60 WU. The other three WUs in cache are v6.55. This one seems that it will last like the one I already done (~8.5 hours in a OC gtx280). If I switch to a v6.55 suspending the v6.60 being crunched, in five minutes the GPU goes from 58º to 65º with the fan fixed to 70%.

I'm now crunching my second v6.60 WU. The other three WUs in cache are v6.55. This one seems that it will last like the one I already done (~8.5 hours in a OC gtx280). If I switch to a v6.55 suspending the v6.60 being crunched, in five minutes the GPU goes from 58º to 65º with the fan fixed to 70%.

Well, someone is lucky ... all I am getting are 6.55 tasks ... :)

Maybe we have to clear out the queue of the tasks generated with 6.55?

Or just doing a limited run test to see if it is working?

I guess I have to wait, sniff, sniff ...

---

···Well, someone is lucky···

Lucky? I suppose you are joking.... I'm happy that now I only have v6.55 WUs!

All the 6.60 crashed in our Windows system, so we removed it for now.


gdf

All the 6.60 crashed in our Windows system, so we removed it for now.


gdf

Thanks for that GDF, some Projects don't bother to Test New Applications & just release the Junk Wu's & let you spend countless hours processing them before you catch it ...

New applications uploaded.

- credits are now more consistent among WUs
- higher process priority in Windows
- several other minor changes
gdf

New applications uploaded.

- credits are now more consistent among WUs
- higher process priority in Windows
- several other minor changes
gdf

How can we recognize the new applications? Do they have a new version?

..... I have a couple showing version 6.61.