Folding Forum

Ah, yes... that's right. It left the other 2 cores for the two GPUs in this machine.

Thanks for the tip on divisibility by 5. Now let me see if I can find a sustainable configuration I don't have to keep an eye on...

Well, I was running it at 30 (not 32, because the FAH client bumped it down to 30 upon install) to, presumably, avoid issues like the one I just ran into with the rank decomposition. The default setting of 30 had been working well without issue for the last month or so when I commissioned this machi...

Nevermind. No, it is not smart enough. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 379034 fah 39 19 1391160 257568 13068 R 1596 0.0 133:59.22 FahCore+ 379060 fah 39 19 1284932 106348 13200 R 1594 0.0 131:33.24 FahCore+ $ taskset -cp 379060 pid 379060's current affinity list: 0-31 $ taskset...

Fair enough. The system has two 8 core CPUs (with SMT). So, I split the slot into two 16 thread CPU slots. Hopefully FAH is smart enough to set the affinity to 1 CPU per WU (or maybe it just punts to the kernel's scheduler?)

Hello, I have received a WU that continually generates the following error message reproduced below regarding there being no domain decomposition for 20 ranks that is compatible with the machine. So, that CPU slot was stuck in a loop, attempting to run the WU, erroring out, and then trying again. I ...

Thanks everyone. Fortunately, it looks like the situation was the same for me. The original WU in question is now showing as received, so no worries. I learned an important lesson here about the WU Status tool: it's not necessarily up-to-date and shouldn't be used to try and identify potential probl...

Okay, I have to admit. I am getting pretty frustrated here. I am not posting to inquire about my point total or the credit for completing this WU. Like I mentioned before, I do not care about the points. I was posting because it appeared that the collection server did not properly record the receipt...

Interesting, I would have expected WU status queries to go one level deeper than the statistics database; otherwise, I wouldn't have bothered posting.

In any case, I'll keep an eye on this and bump the thread if this WU still doesn't register in the next week or so.

Thanks. I'm not really concerned about the stats/credit -- just the loss of the work. Even if the "points" aren't updated, I would think that the WU status tool would still be correct @ https://apps.foldingathome.org/wu (unless there is a "real" problem, of course). Otherwise, th...

Hello, I observed the following a few hours ago and thought I would report it. Log for WU [Project:11759 (Run 0, Clone 5086, Gen 42)] (Upload Successful. Final credit estimate, 132696.00 points) 14:36:48:WU00:FS01:0x22:Completed 1000000 out of 1000000 steps (100%) 14:36:50:WU00:FS01:0x22:Saving resu...

Excellent! Seems to be working now, thanks @uncle_fungus!

Interesting. Good to know I'm not the only one having an issue with Project 11758 32hrs since my original post, and my client is still attempting (unsuccessfully) to send these two "problem child" failed WUs: 11758 (0, 3765, 0) 11759 (0, 10513, 1) It doesn't seem to be jamming up the works...

Hello, I'm new to Folding@home, so I apologize if the solution here is obvious/trivial. For about the past ~15 hours maybe, I have 2 FAULTY WUs that are failing to upload. All NO_ERROR WUs continue to upload just fine (with the occasional hiccup, of course, due to the unusually high volume). I have ...

Thanks for the replies. I am new the Folding@home project, so I did not know if this issue was already known or in some way being mitigated on the backend. I don't want to be misunderstood here. Clearly, points don't matter. We are all contributing resources to solve very real problems in times of n...

Thanks, Joe! No worries, was just hoping there might be a simple fix from my side. Strange how it only affects some users and not others. Bizarre. Good luck on the upgrade.