Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 177
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My reading of prior responses and the option itself is that you'll only get GPU work for the researches you've selected i.e. no HCC selected, no GPU version pf tasks send, when available. Well if I am forced to also run the HCC CPU jobs in order to be able to get the GPU jobs, I guess I won't be doing any GPU work... ![]() I really want to run the GPU HCC but I want to reserve the CPU for other projects... |
||
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
tomcast...that is exactly my concern. I don't mind sacrificing some CPU time to feed the OpenCL work, but I would rather the rest go towards the other project goals I have. I have already hit my HCC goal but would rather my GPU's to go to use here. I guess we must take it with stride as they figure things out. This is another reason for my suggestion of an option for HCC GPU only previously. However, I understand they have enough on their plate and we should just be content for now.
----------------------------------------![]() ![]() ![]() ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Why not read what knreed has said before jumping the gun? I gave the present function. This is what's looked further into: http://www.worldcommunitygrid.org/forums/wcg/printpost_post,367408
--//-- |
||
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
We are not turning on validation yet. There are some odd cpu time and claimed credit values being reported/generated. We need to resolve that first before we turn those on. Having returned two results since the upgrades, it appears that the claimed credit is being doubled. My linux machine claims 26.8 credits per hour, but both results are showing 53.6 credits per hour. GFAM_ x1uh5_ PfENR_ 0009490_ 0096_ 0-- Pending Validation 3/3/12 03:32:53 3/7/12 00:35:00 3.84 205.9 / 0.0 GFAM_ x1uh5_ PfENR_ 0009490_ 0065_ 0-- Pending Validation 3/3/12 03:32:53 3/7/12 02:16:27 3.61 193.4 / 0.0 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We are not turning on validation yet. There are some odd cpu time and claimed credit values being reported/generated. We need to resolve that first before we turn those on. Having returned two results since the upgrades, it appears that the claimed credit is being doubled. My linux machine claims 26.8 credits per hour, but both results are showing 53.6 credits per hour. GFAM_ x1uh5_ PfENR_ 0009490_ 0096_ 0-- Pending Validation 3/3/12 03:32:53 3/7/12 00:35:00 3.84 205.9 / 0.0 GFAM_ x1uh5_ PfENR_ 0009490_ 0065_ 0-- Pending Validation 3/3/12 03:32:53 3/7/12 02:16:27 3.61 193.4 / 0.0 =============================================================== My hex core is showing higher claimed credit now to on C4CW tasks. Before / 1.96___48.4 / 43.9 After / 1.96____109.3 / 0.0 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My 6.10.60 / 64-bit client for Win7 has downloaded 32-bit jobs for C4CW 6.40.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My 6.10.60 / 64-bit client for Win7 has downloaded 32-bit jobs for C4CW 6.40. Me too... But it looks like they are all repair jobs _1 and _2 ![]() I guess they are trying to knock-out a bunch of redo jobs before they get back to regular 64 bit jobs... |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm getting double points on my Linux machine as well. 11.10 boinc version 6.12.33 64-bit.
----------------------------------------C4CW, CEP2, and SN2S all affected. All in PV. [Edit 1 times, last edit by Former Member at Mar 7, 2012 3:35:51 AM] |
||
|
keithhenry
Ace Cruncher Senile old farts of the world ....uh.....uh..... nevermind Joined: Nov 18, 2004 Post Count: 18665 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Just noticed something that could delay WUs ready to validate to wait days before that happens (if I understand things correctly). Looked at my Results Status and filtered for Pending Validation. Clicking on the WU link for each task, for those WUs where both I and the wingman had returned the WU, both of us showed Pending Validation status as expected. That would mean once the validators are running, we'll get credit for these. However, for every single WU (happened for both GFAM and SN2S projects though not necessarily related to that) that had both myself and wingman as PV, the TRY VALIDATION link displayed. Clicking on that link pops the message "Scheduled for validation" and the TRY VALIDATION link is then gone. As I recall, a WU with this TRY VALIDATION link will not otherwise validate until it reaches the current reporting deadline, which could easily be days down the road. Wanted to report this as a possible issue just in case I'm somehow right!
----------------------------------------![]() |
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1960 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Clicking on that link pops the message "Scheduled for validation" and the TRY VALIDATION link is then gone. As I recall, a WU with this TRY VALIDATION link will not otherwise validate until it reaches the current reporting deadline, which could easily be days down the road. Wanted to report this as a possible issue just in case I'm somehow right! Well, knreed mentioned that the validator has not been turned back on, so I would not expect the "TRY VALIDATION" to work in the first place.![]() He mentioned that they did this because they noticed that there are abnormal credits claimed, so it will certainly be a day or two before that part is solved and validation will start again. And with another scheduled downtime on Thursday, I would not expect to get actually any credits before the weekend... Ralf ![]() |
||
|
|
![]() |