Thanks for the reply. I've made a few small changes, but the fact is that the laptop is not heavily used and was given very nearly free reign for BOINC when not in use, and did not run until the laptop had been unused for 5 minutes.

At my last job, I had access to multiple systems running lab machines, and let's face it, most of the time they were entirely idle. I had BOINC on all of them, running when the lab system was idle, with no impact on lab work. I did have another laptop here running BOINC, but when it started making noises like the fan was going to fail, it's shut down for now.

PrimeGrid sends a lot of relatively small jobs, always complete early. I observe there that the estimated time to completion drops as soon as the task is begun.
Einstein sends a number of jobs, fewer and larger than PrimeGrid and always complete early.

Right now I've put both those projects on 'no new tasks' and I'll see what happens after that, and update later.

I endorse Grant's suggestions, but I'll just mention some slight differences I use on my relatively new laptop.
I worry about temperatures/cooling too, but I'm getting away with 50% of the CPUs without fan problems or throttling.
By all means start with 25% (2 of 8) cores and if it works much better, try 37.5% (3 of 8) before stretching to 50%.

In terms of time unused before Boinc starts, clear the fields and unselect them. I believe this defaults to 1 minute, which I think is plenty.
Lots can happen in 5 minutes - even just touching the mouse or keyboard. I always suspect this makes a huge difference with no benefit to you or Boinc.

In fact, I have everything unselected on the computing tab, except "Leave non-GPU tasks in memory while suspended"

---

Right now I've put both those projects on 'no new tasks' and I'll see what happens after that, and update later.

One thing i didn't notice earlier with Einstien- it takes you 6 days to return work there.
Here the deadline is 3 days.

Make sure "Use at most xxx % of CPU time" is set to 100%, Set your cache to

Store at least            2.0 days of work
Store up to an additional 0.01 days of work

If you feel the need for a cache (given the present issues, i'd suggest no cache at this stage; 0.1 days and 0.01 additional days).

And as Sid posted, make sure When to suspend isn't selected at all (the default is actually 3 minutes)- especially so if using only a couple of cores/threads. There'll be plenty left over for other programmes & the Operating System; no need to suspend BOINC.

Right now I've put both those projects on 'no new tasks' and I'll see what happens after that, and update later.

At the moment- nothing will happen. There is no work here at Rosetta at present, and when there is you've got a 1030min window to get some, before it's all gone.

I'd suggest re-enabling work for the other projects, and see you processing times improve, and work being returned much, much earlier (it needs to be done in less than 3 days to process work here).

---

Grant
Darwin NT