GPU WU issues spreading to CPU WUs

[LonePalm]

Thanks. This is frustrating.

I still don't understand what is so magical about rebooting the computer that ALWAYS gets a new WU immediately.

[bruce]

This is is a vexing problem ... or maybe two different problems with both differences and similarities.

Perhaps the setting CPU:7 is part of the problem. A number of projects have higher failure rates when run with a setting of 7. Many of those projects have been restricted and will not assign when you use that setting. I don't have any way to judge how many WUs are available/unavailable to your client but how about setting that number to an even number (say 8 or 6) and see if it helps.

[LonePalm]

Bruce,

That is not something I have set.

I have 8 cores on my CPU. Doesn't the GPU reserve one core for its use?

How and where should I make the change in the configuration?

[P5-133XL]

You can change the number of CPU cores using the advanced control accessed from the system tray. Click configure->go to the slots tab and double click the CPU slot. From there change the number of threads from -1 (Automatically choose) to an explicit 8 or 6.

[LonePalm]

If I make it an 8 will it hurt my CPU folding?

Right now it looks like one core is being reserved for the GPU.

[bruce]

Setting it to 8 will cause some competition between the GPU slot and the CPU slot. I've seen mixed reports about the nature of that competition so I can't give you a definitive answer about how CPU:6 compares to CPU:7 or to CPU:8. Certainly if CPU:7 is wasting much time because it has no WU, it will quickly become the least desirable of the three.

My GPU uses 100% of a CPU core, but only about 10% of the time. Whether processing with 8 cores for 90% of the time or processing with 6 cores for 100% of the time is the best, given the precise configuration of your system can only be determined by you. Try all three and pick the one that works the best over the long-term.

[P5-133XL]

If you have a CPU core used by the GPU then 6 is likely far better than 8.

[bruce]

Thanks. This is frustrating.

I still don't understand what is so magical about rebooting the computer that ALWAYS gets a new WU immediately.

Rebooting is a magical cure when you've become overly impatient.

The client is designed to retry after longer and longer intervals to protect servers from overloads. This is critical after a server has been down for a while and everybody's client is waiting for the server to be restarted so a huge load hits the server all at once. If your client has retried several times at short intervals, the client will wait longer before the next retry -- but that may beyond your tolerance threshold.

The only time I've seen a client actually stop retrying is after your ISP or router generated an error causing an upload to time-out. That's a reported bug.

[LonePalm]

What makes a WU request immediately after rebooting different from a WU request normally generated?

The first ALWAYS generates a new WU. The latter may or may not generate a new WU.

[bruce]

What makes a WU request immediately after rebooting different from a WU request normally generated?

The first ALWAYS generates a new WU. The latter may or may not generate a new WU.

* The time-interval between the first attempt to get a WU and the next attempt is different.
* The condition of your cache is different.

[LonePalm]

With a fresh boot, there is no interval between requests. The client issues only one request and it gets a WU.

What changes in the cache?
Why does this affect whether or not the server issues a new WU?

I ask this only to try and understand what is going on.

[7im]

Please describe your connection to the internet. Wired, wireless, devices, models, ISP, speeds, etc.

Please also describe all of your Anti Virus, FireWall, Anti Malware, etc.

[LonePalm]

My ISP is Comcast High speed Internet.
The cable modem is a TM722.
The wired router is a D-Link DI-624 wireless is available for my cell phone.

Windows Firewall is OFF.

ZoneAlarm Extreme Security Firewall and Anti-virus is installed and operating.
All F@H programs are specifically white listed with full access.
I run Spybot Search & Destroy. I've never had that pop-up regarding anything with F@H

I also use Malwarebytes once a week. The last deep scan was Monday with no hits.

[7im]

PC is using ethernet to cable modem?

[bollix47]

Can you please completely uninstall ZoneAlarm just to test if your problem disappears? You can always reinstall it again. Simply disabling ZA isn't enough.

Is MSE also running? It's never a good idea to run two virus protection programs at the same time.