Moderators: Site Moderators, FAHC Science Team
Breach wrote:Same observations, 13416 (1297, 133, 1) for example - PPD is lower than usual by about 25%.
HaloJones wrote:just for some balance
P13416 (R376, C170, G1) running around 35% above average
P13416 (R791, C148, G1) ditto
Sparkly wrote:These 13416 things are now spending so much CPU and System resources away from the GPU that the GPU doesn't really do much, because of all the waiting, so maybe it is time to take a closer look at the general CPU to GPU handling of WUs in software. (R1166 C7 G2)
Bastiaan_NL wrote:Are you still running a CPU client?
Joe_H wrote:You keep bringing this up, the projects would not complete on CPU folding within the timeframe necessary to get the results to other researchers.
Sparkly wrote:Joe_H wrote:You keep bringing this up, the projects would not complete on CPU folding within the timeframe necessary to get the results to other researchers.
Who said anything about running these projects on CPU, what I am saying is that the CPU to GPU communication is creating an insane amount of overhead that shouldn’t be there in the first place, this is about programming and nothing else.
Sparkly wrote:...so maybe it is time to take a closer look at the general CPU to GPU handling of WUs in software
Joe_H wrote:On top of all of your other complaints, how else is it to be taken?
HaloJones wrote:P13416 has huge variations so you're not comparing apples to apples.
e.g. two 1070s in the same machine, same PCIE speed, same overclock, same drivers, same OS.
P13416 (R577, C150, G1) - TPF 02:20 for 1307292 ppd
P13416 (R910, C67, G0) - TPF 03:14 for 799240 ppd
Don't get hung up on this. Some P13416 are super quick and give great points, some are the opposite. Overall, it balances out.
Return to Issues with a specific WU
Users browsing this forum: No registered users and 0 guests