Too many WUs

When you first bring a new host 'on-line', there are a few things you can do to make the startup a bit less confronting. One of those is to make sure you have a relatively low cache size in your computing preferences. If you are setting up a new account, the default prefs are reasonable and you shouldn't get this issue. If you are about to re-invigorate an existing account, you should check all your settings on the website before you fire up the BOINC client.

There are two settings for work cache size, the first two items under the 'Network Usage' heading in your computing preferences on the website. Leave the first one as close to zero as possible if you have an 'always on' connection. Put the second one to 0.1 days to start with. This will essentially allow you to get a single task per core and will have a very beneficial effect on the initial crazy volume of downloads you may otherwise get if you leave it at something like 1.0 days or higher. If you had it at 1.0 days, you wouldn't get all that many tasks but you would most likely get a huge volume of large data file downloads that is quite worthwhile to avoid. The best way to start is to set 0.1 days and watch BOINC get a task for each core probably in a series of requests about a minute apart. Then you can GRADUALLY increase the setting in a number of small steps until you get to the cache size that is appropriate for your requirements.

Another tip for having an efficient startup is to set your final preferences to what you want them to be on the website and then to temporarily override these with local prefs just for the startup. If you ultimately want a 3 day work cache set it that way on the website but use local settings in BOINC Manager to set the 'extra days' setting to 0.1 days. Gradually build up the local setting in small steps and when you get to what you want, use the 'clear' button in the local prefs pane to revert to web-based prefs.

Many people seem to come to E@H with rather excessive cache settings - perhaps a relic from Seti behaviour. If E@H is your only project, a setting of 3 or 4 days would be all that you should need. The more projects you attach to, the lower this value should be. In your case, I'm guessing you have a total cache setting of 10 or more days and BOINC is probably underestimating how much time each task will take.

You don't really need to set 'No New Tasks' (NNT) - just reduce your cache setting to (say) 3.0 days total and allow your host to crunch 24/7 (or do some selective aborting) until things become a bit more manageable. I can't see any completed tasks yet - are you actually allowing your machine to crunch? When the first tasks are returned BOINC will quickly develop better estimates for crunch time and if these are longer than the initial estimates, crunching may kick into high priority mode. It may already have done that.

If you need further help, please ask. Your situation is quite recoverable if you want to.