Average time of WU is 1 hour, let's say 3 hours on slowest computer.
You set deadline 3 days, therefore you dont need WUs back THAT fast.




1) Well, im not crunching first day and know what is quorum, redundant result and how WUs are sent and resentThe FAQ is sometimes useful.

3-day deadline: There will be wus, which need more than 24h to complete.rilian hat geschrieben: 1)
Why do you set 3-day deadline? 1 day is more than OK, to me... With this you will cut off too slow computers, encourage participants be 24/7 online, and this will benefit project.
Also in FAQ you say you dont allow large caching, but from "slow" 2Ghz computer details i see "Maximum daily WU quota per CPU 500/day"
Just trying to understand project settings..![]()
Currently there is no strong wu dependency. The only thing is, that we first must run some cmcalibrate wus, which are than the base for thousands of cmsearches.rilian hat geschrieben: 2) Sorry going offtopic, but are there WU generations, like N+1th WU of one generation uses results of Nth WU, or Wus are independent.

In fact, with Linux some need 80 hrs, with Windows some do even require 160 hrs or more to complete. And due to the diversity of applications and the additional work unit heterogeneity for a given application, we cannot practically tweak the project settings every day.yoyo hat geschrieben:3-day deadline: There will be wus, which need more than 24h to complete.
