I have now enough wu's for the next 16 days.
How is this possible.
The limit is 10 days as far as I know.

---

Goodbye Seti Classic

Not entirely true.
There are 2 settings in preferences.

maintain enough work for max 10 days
and additional

If your seetings are 8 / 8
Its 16 days.

---

With each crime and every kindness we birth our future.

In that case, I will change it to 5 / 5 and see what will happen.

Thanks.

---

Goodbye Seti Classic

I do 10 days and connect every 0 (always connected). Seems to level out right around 10-10.5 days.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I do 10 days and connect every 0 (always connected). Seems to level out right around 10-10.5 days.

Apples and oranges. That works on V6 and older. With V7 which S@NL - XP_Freak uses, that would cause the cache to drain to nothing before work fetch would happen.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

I've noticed that when you set a large cache and you are running a number of projects, some of which may not have a high level of WUs or are running in a Virtual Machine such as BOINC_VM, then you might find the busier Projects (those that pump the cache full) don't play well with others.

I run SETI, Einstein, LHC (has little work), and LHC/T4T. Currently I'm running 0.5/0.5 on the cache settings and still see SETI and Einstein "hogging" the cache which means I miss work from the other two Projects. When LHC has some work then the cache is almost always full and when work completes on the LHC/T4T Project there is a long delay before the Project loads its next WU. (T4T loads one WU that runs approx 24 hrs but since it is in a Virtual Machine the VM communicates with the servers and receives multiple project tasks under the single WU.)

My understanding is that the gurus at BOINC are working to correct this situation but for the time being it is important to understand the interaction between Projects and the cache setting. If all your Projects are pretty much equal then it's no big deal.

---

I've noticed that when you set a large cache and you are running a number of projects, some of which may not have a high level of WUs or are running in a Virtual Machine such as BOINC_VM, then you might find the busier Projects (those that pump the cache full) don't play well with others.

I run SETI, Einstein, LHC (has little work), and LHC/T4T. Currently I'm running 0.5/0.5 on the cache settings and still see SETI and Einstein "hogging" the cache which means I miss work from the other two Projects. When LHC has some work then the cache is almost always full and when work completes on the LHC/T4T Project there is a long delay before the Project loads its next WU. (T4T loads one WU that runs approx 24 hrs but since it is in a Virtual Machine the VM communicates with the servers and receives multiple project tasks under the single WU.)

My understanding is that the gurus at BOINC are working to correct this situation but for the time being it is important to understand the interaction between Projects and the cache setting. If all your Projects are pretty much equal then it's no big deal.

I run a project that is busty also. The Lattice Project. I also have 2 projects that run for weeks at a time for one WU. I could get one of those WU and 7.0.x will not ask for work for almost a month even though I have around one year to finish that WU (why Hello CPDN).

---