• 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.

Anyone working on UD Cancer.

virus

Member
Anyone who is working on United Devices Cancer project. Could you please tell me if it uses a work unit like D.net and SETI do. If so, could you post any statistics you have. I need to know the CPU type, CPU speed, amount of ram, and work units a day or hours per unit. I am using this info to add UD:Cancer support to the CPU Archive.
 
I know that the work unit size for UD is variable like seti. It seems to be dependent on ram and cache. Ram usage is fairly high. I thought i read that it was at 25mb. I just took ud off my last computer today. Thats all the info I have.
 
Actually the SETI work units are all the same size but they take different amounts of time depending on the data inside the WU. I dunno about the UD work units. Are they different sizes or are they like SETI's?

Rob
 
The UD WUs consist of 100 molecule (200 now I believe) that each can have 100 submolecules. Some units just fly by and then get stuck on a molecule that takes forever to finish. This is why the time is so variable. I think they are weeding out molecules that take a really long time to finish so times may be more consistant now.
 
SETI work units were fairly even, with the old clients. All my old SETI stats are now useless. I don't think I will be updating them anymore.

I guess the days of linear work units and statistics are almost long gone. All the new projects (UD:Cancer, Folding@Home, Genome@Home, etc) have different sizes and multiple types of work units. Folding and Genome don't give the exact time it takes to complete the work units. Proxies are also completely out of the question. 🙁

Long live D.net!
 
Back
Top