Why so short Workunits?

Why are the Workunits here so short? It must bee a huge overhead for the server with workunits running as short as 20 seconds.

News

New Modfit Runs
Hey Everyone,

Just a heads up, I will be starting new runs over the next couple days that will have a different step size in a computationally intensive section of our code. Through some work we did, we found that this step size could be optimized and reduced to improve the speed at which our code runs without sacrificing accuracy. We expect to see these runs complete in about 1/5th the time depending on the platform. Credits will hopefully still be calculated correctly, but if you think they are not for these runs please post here. If these runs cause you any trouble with these runs or you notice you stop receiving work units please post that here too. These runs will all include the tag _fast_ in the work unit name so it should be easy to track.

For now, these optimizations will only be used on the Modfit code, but in the near future we plan on also using them on original separation code, too.

If you have any questions about this optimization or problems, please let me know,

Jake

Aside from the new _fast_ runs as mentioned.

Milkyway have always had short workunits with fast turn around times so that the eveloving testing parameters are checked and that any particular result does not become stale.

Just Running on a CPU the Milkyway@home Simulation could take an hour or so. and the Usually Seperation or Seperation(Modified Fit) takes about 2 hours.

The N-Body Simulation might be a bit different.

Double Precision GPUS the Only GPUs that Milkyway utilies a MultiThreading are probably much faster.

It's just the way the Milkyway Project utilises the volunteered resources.