| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: 7 Day Deadlines for Test |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 90
|
|
| Author |
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3294 Status: Offline Project Badges: 
|
Try 48 hours next.
----------------------------------------AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Falconet,
I have it in my plans, need to see if I get approval :) However, first I need to get the 24 hour deadline renabled and capture the data with random send intervals to make sure i'm doing apples to apples. Thanks, -Uplinger |
||
|
|
halldor.usa
Advanced Cruncher USA Joined: Nov 24, 2006 Post Count: 115 Status: Offline Project Badges: 
|
Thanks for keeping us posted @uplinger. My current badge goals are on this project.
|
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
I, and I assume others, am getting these FAHB units in batches at random times. Is there a way to spread out the despatch times so the flow is more even?
I have noticed that on my 3770K machines that are running mostly MCM, FAHB run times are significantly longer if many FAHB WUs are run simultaneously. The same goes for MIP WUs. I know that I can restrict max_concurrent in an app_config file, but that would increase the time they spend in the work cache before they start to run, and slow your turnaround times. These effects on runtimes are probably due to the relative sizes of the WUs' RAM requirements. In Windows, The "Memory (Private Working Set)" numbers are around 250-300MB for an FAHB vs about 40MB for an MCM. The big FAHB tasks probably require more CPU cache than the MCMs, and with many FAHB competing for the limited 8MB total (L3), they run more slowly. |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3294 Status: Offline Project Badges:
|
Thanks for the update, uplinger.
----------------------------------------AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
kapetan_proton
Cruncher Joined: Dec 10, 2008 Post Count: 37 Status: Offline Project Badges: 
|
I have noticed that on my 3770K machines that are running mostly MCM, FAHB run times are significantly longer if many FAHB WUs are run simultaneously. The same goes for MIP WUs. I know that I can restrict max_concurrent in an app_config file, but that would increase the time they spend in the work cache before they start to run, and slow your turnaround times. That can be result of hyperthreading. Leave only four tasks active and they will finish in less time. But, why do that except for more points scored that way? It's because it running 8 threads, not real cores. |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
I, and I assume others, am getting these FAHB units in batches at random times. Is there a way to spread out the despatch times so the flow is more even? By Random times, this is by design. When we load workunits into the grid it is a task that is kicked off every 30 minutes. However, due to members pressing update on those specific minutes and soaking up the work units loaded, we have "randomized" the time within the 30 minute window. Running these tasks to load work are database intensive, which is why we are not running them sooner. Previously on WCG we were only able to run these tasks once every 6 hours. Thanks, -Uplinger |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Haven't seen any new WUs for days.
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7574 Status: Offline Project Badges:
|
Haven't seen any new WUs for days. I am getting a few random ones here and there. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Collected the first bits of information. I'm turning the project back to 1 day deadlines.
Note: It will take the project about a week to get back to processing speed as before. Thanks, -Uplinger |
||
|
|
|