I increased the length of wu in order to ease the workunits validation.
Now, the new workunits will run for 6 hours.

---

WU volume picking up?

---

Click here to see My Detailed BOINC Stats

Bonsoir Sébastien,

Soucis actuels, tous mes WUs calculés sur Lollipop ne sont pas pris en compte.
Sur mes autres supports no soucis évidemment.
WWC sur Lollipop seulement actuellement.

@+

---

I apologize but I'm kind of confused between the workunits and the regular BOINC tasks?

---

Kindly visit my website

I apologize but I'm kind of confused between the workunits and the regular BOINC tasks?

G'Day Habi LK,

The regular BOINC tasks do the work of the project they belong to.

The WUProp tasks are part of this project and run basically in memory with a few minutes of CPU time here and there.

What WUProp tasks do is monitor other BOINC tasks to collect data on them, such as run time and memory requirements.
This data is collected from everyone running this project and then uploaded to this project where you can check out the information on the website and help you work out what other project applications you can run or want to run.

That is a basic run down on the project.

Each WUProp work unit runs for 6 hours no matter how fast your computer is, as it has nothing to do with processing data and uses vitrtually no CPU.

A lot of us use it to chase as many applications as we can to see how many hours we can generate per application and gain badges accordingly.

To get your first badge star you will need to run 20 applications and run them for 100 hours or more to gain the first Bronze star.
It does not take that long when you consider that a 4 core computer generates 24 hours per core per day (24*4 = 96 hours/day).

Hope this helps.

Conan

---

I have many computers and slow connection so boinc clients are only allowed to transwer data between 00:00 and 8:00. How does it affect my score or your data you can get from my thingies?

---

I have many computers and slow connection so boinc clients are only allowed to transwer data between 00:00 and 8:00.

Same here (sparing useless details and avoiding passive aggressive competition). However, I went for different schema: cron-job, each 4h, summons interwebs, then notifies clients than tubes are OK for some speculated time-gap (10min per core). Turns out, it wasn't working that well (for different reasons).

How does it affect my score or your data you can get from my thingies?

So, after anxiety inducing puzzling observations, I've put myself together and made peace with client now (yes, peace involved scripting). And I dare to declare this: given host is working 24h/day, such host can do up to 55cobblestone/day; if such host does 55..40 of WuProp it's underreporting; if such host does less then 40 it's underworking. Now, it's up to you what would you do with that expert opinion ;) Just remember, not giving a thing -- is an option.