• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why so few TeAm mates doing CPDN?

Shuxclams

Shuxclams

Diamond Member
I am just wondering why we dont have a stronger CPDN TeAm, seems like a very good 3rd choice behind S@H and E@H











SHUX
 
Well, take how many hours a seti-wu will take, multiply with 10, and you have a rough estimate of how many days a CPDN-wu will take on the computer...

CPDN-wu is very long, from 3 weeks and up is normal, takes 650 MB disk-space, and has a reputation to crash on many "stable" overclocked computers... and some non-overclocked.

Initial wu-download is large, around 10 MB, and result-size is around 5 MB. Still, due to the very long crunch-times, this is an excellent project even for dial-up. Also a good backup-project for all other BOINC-projects, since nearly 1 years deadline.

BTW, the current model is the small & fast model, the next released should be the sulphur-cycle-model, with expected crunch-times from 2 months...
 
You're right Rattle. When I move back to Germany, I'll load CPDN on my laptop computer. I don't know when the next time will be when I have some i-net access so CPDN is a very good project (like DPAD) to do in such a case.
 
I really like CPDN. I was wondering why the team is not more active on the project when I was solely crunching on it. But, as long as the work units take, you still get trickle credits. So the defense about long work units does not really make sense to me. The credit and statistics is almost just as active as any other BOINC project. True, the final results are a long way out, but that is the actual science and does not unltimately effect your points.

On a second note, I think CPDN is one of the hardest projects I have ever run on my machines. I have never had it crash a single one, o/c or not, but it is really hard on them. In my experience, it slowed some down when working with other applications, and overall system response time seemed slow. CPDN is very dependent on memory, and lots of it. That is the biggest reason I may see for low adoption, and the reason why I can run only a few non-critical machines on it.
 
Too big for dial-up, too slow for me. And it seems to me that, while development was going on, the question was answered by other non-distributed projects. So I personally see no point to it.
 
That's also my point. It doesn't make much sense to use lots of CPU power on CPDN to see what the climate will be in 50 years without many nations - including the US - not taking the proper steps to reduce emissions and the green house effect. The computers running CPDN will actually contribute to a worse climate because of the power they use, although that's only a tiny bit, but it's still something.

🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top