Back in Black
7 Dec 2020 3:39:27 UTC
Topic 224162
(moderation:
Hello team!
After 3 years, I'm back to crunching Einstein. I'm glad my Fiji boards are still relevant with this project. Anywho, just wanted to say hello and that I'll be trying to get up the leaderboard once again. Watch out. LOL jk jk
Ross
You may have problems with
)
You may have problems with BOINC going into panic mode shortly. You have allowed both types of GPU search and they will tend to disrupt each others crunch time estimates. The best way to cope with both at the same time is to keep your work cache size small - really small - maybe as low as just a few hours, particularly until you get a good feel for a sensible value. This is important so as not to risk a big bunch of GW tasks with way too low estimates. These get artificially lowered by completed tasks for the other search. The two searches do have strong effects in opposite directions on each other.
The GW tasks have a 7 day deadline only, and you already have over 700 of them "in progress". If you process some fast finishing GRP tasks it will lower the estimate for GW tasks and you'll likely get a bunch more of them. The best way to prevent such overfetch is a small cache size.
What work cache size are you currently using?
Cheers,
Gary.
Hi Gary! Thank you for your
)
Hi Gary! Thank you for your input.
I'll find out what the cache size is on that computer. I think I set it pretty high because from what I can remember, I last worked on milkyway@home and needed as many tasks as possible since my titan blacks were eating them all up.
I believe I will finish all the GW tasks in 4 days and some hours. I may slap on a fury x in there to finish faster so my average won't decline so much. I've already unchecked that application on that computer and plan on building another specifically for that task.
Welcome back!!
)
Welcome back!!
Thank you!
)
Thank you!