Hi,
could we have a little longer deadline please ?? 1 week (maybe more) for example.
Thanks.

Pourrait-on avoir une date limite d'envoi un peu plus loooonnngue ? 1 semaine (ou +) par exemple. Merci. (Ps :je ne crunche pas 24/7)

Hi,
could we have a little longer deadline please ?? 1 week (maybe more) for example.
Thanks.

Pourrait-on avoir une date limite d'envoi un peu plus loooonnngue ? 1 semaine (ou +) par exemple. Merci. (Ps :je ne crunche pas 24/7)

The design of each WU is to collect BOINC data over a 24 hour period, return the result get another WU and do it all again.
Therefore only one WU at a time is needed and it would be pointless to have WU's returned a week after being sent out as the data gathered would not be over a straight 24 hour period but on and off over a 7 day period.

The WU runs straight from start to finish (if you run your PC 24/7), it runs mostly in memory so has little affect on PC performance.

You may want a longer deadline if your computers are not running all the time, perhaps this is what you are meaning here, that your PC is turned off at night?

---

You may want a longer deadline if your computers are not running all the time, perhaps this is what you are meaning here, that your PC is turned off at night?

My own computer is on 24/7, as it's a kind of hobby for me.
On my parents computer BOINC is running as it's designed for: Only using spare CPU-cycles if the computer is on anyway. And they don't use their computer that often, sometimes 1h a day, sometimes 4h, sometimes no use for 2 or 3 days. They are online once they start the computer, that's no problem.

I have to chose projects carefully for that set-up: short WUs, long deadline, small cache, no beta.
I have this computer as well manageable via BAM!, but I wonder if this set-up will lead to errors or not. They will most certainly never get 24h crunch time in 5days calendar time. They have an imho not so uncommon set-up for computers outside the circle of the usual forum folks;)

So:
Is WUProp as well possible to gather information from this kind of set-up, or is it only for the nerds like me who keep it running 24/7?

---

Grüße vom Sänger

I don't think longer deadlines could be a solution, shorter WUs (smaller credits) could solve the problem of non 24/7 hosts.

But we have to keep in mind that this project is for statistic purpose only, so if the number of hosts validating WUs in time is enough and is representative maybe things don't need to change.

Hi,

You may want a longer deadline if your computers are not running all the time, perhaps this is what you are meaning here, that your PC is turned off at night?

Exactly, what I mean.

So:
... or is it only for the nerds like me who keep it running 24/7?

That's what I'm afraid of.

if the number of hosts validating WUs in time is enough and is representative maybe things don't need to change.

sad not to allow any cruncher to report results even if they crunch slowly.
(c'est le jeu, ma pauvre Lucette !)


But, that's OK. I was just asking.

Good luck.
Whatever, expect to see one of my Wu on a crunchin week-end ! ;)

But we have to keep in mind that this project is for statistic purpose only, so if the number of hosts validating WUs in time is enough and is representative maybe things don't need to change.

Form follows function ;)
As the purpose is to gather information about WU properties, it's probably fine to exclude those computers that will not give that much information.
In that respect 100 nerd computers, best by some ATAs, will give nearly enough, and the meagre information possible by the mentioned "parental set-up" isn't really relevant.
That's fine with me. There's no need to keep every single computer connected if it doesn't deliver any useful information.

---

Grüße vom Sänger

But we have to keep in mind that this project is for statistic purpose only, so if the number of hosts validating WUs in time is enough and is representative maybe things don't need to change.

Form follows function ;)
As the purpose is to gather information about WU properties, it's probably fine to exclude those computers that will not give that much information.
In that respect 100 nerd computers, best by some ATAs, will give nearly enough, and the meagre information possible by the mentioned "parental set-up" isn't really relevant.
That's fine with me. There's no need to keep every single computer connected if it doesn't deliver any useful information.

Not a good idea, looks like lobbyism for ATA. And only nerd computers will narrow the baseline, shift the database toward highend PCs. The gatered informations would less usefull for the other projects.

I think shorter WU time will do it.

Because the "average" machine for a non-nerd runs 4 hours a day, in which it is used for ~1 hour. Means spare time=3 hours. Multiplied with 5 days deadline means max runtime 15 hours for the average "this is my typing machine and internet" computer.

And doubling the deadline means very much longer to build a good database. You need more than 2 or 3 WUs to know if project x really needs only 2 hours on computer y because there MAY be workunits running much longer than the 2 or 3 already inside the database.

And there are much of these machines running for seti or maybe 2 or 3 other projects - it will be interesting to see WU runtimes on these machines for the different projects. Because with the help of this projects the not-so-average user with a slow machine can decide "hey my computer is also good enough to crunch for THIS or THAT science-project" without asking in the forum.

For example I found a Transmeta Efficéon Processor in the list - I didn't even knew that such a thing existed. Had to google it up ^.^

Ah, by the way, it is collecting data for the cpu-apps. Is there also an overview of the gpu-apps?

New workunits will be shorter, 12 hours instead of 24 hours.

---

Noticed the run time has halved but the credits have remained the same! I am by no means complaining. :-)

Noticed the run time has halved but the credits have remained the same! I am by no means complaining. :-)

Well if taking the processing time of 24 hours (or 12 hours) for just 50 credits, you are not getting very many credits per hour are you.
This of course is not taking CPU processing into consideration just the time it is using your resources on your computer (includes CPU, Memory, Power, etc), so not a problem for me.

---

Another solution could be to have a fixed wall-time runtime, like DynaPing. There the WU always completes after 24 hours of wall-time, regardless of actual CPU-runtime.

This can however be a problem for granting credit. Can maybe be fixed by something like:
(totalCreditPerWU/secondsPer24H)*actualRunTimeInSeconds

Because with the help of this projects the not-so-average user with a slow machine can decide "hey my computer is also good enough to crunch for THIS or THAT science-project" without asking in the forum.

EXCELLENT point. This is EXACTLY why I use this project.

---