| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: CEP2 beta for windows - Version 6.25 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 311
|
|
| Author |
|
|
captainjack
Advanced Cruncher Joined: Apr 14, 2008 Post Count: 144 Status: Recently Active Project Badges: 
|
Hyperthread run time comparison. One of my boxes has 8 cores and is hyperthreaded so it normally runs 16 jobs at a time.
When the clean energy beta jobs were released yesterday, the box downloaded 8 beta jobs. I manipulated tha queue so that all 8 energy jobs ran at the same time along with 8 c4cw jobs. All jobs completed normally. The energy jobs ran 10-12 hours. The box downloaded another 8 clean energy beta jobs. I set the max cpu's to 8 (50% of available) and manipulated the queue so that the box would run 4 energy jobs along with 4 c4cw jobs for a total of 8 jobs. All jobs completed normally. The energy jobs ran in 6-7 hours. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've completed 5 beta units on my Core i7@3.35GHz. One is still pending validation, but 4 have validated. So far, so good.
----------------------------------------
So, an average of 24 credits/CPU hour, or about 2,300 credits per day running 4 cores. [Edit 1 times, last edit by Former Member at Sep 23, 2010 1:57:40 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, an average of 24 credits/CPU hour, or about 2,300 credits per day running 4 cores. Just FYI, the CEP2 blocks running under an Ubuntu VM on the same hardware generate about the same credits per hour. |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
Well, so much for the 12 hour cutoff on this wu as it is now at 13:31 hours & 19.6% complete. Wingman got it at the same time and still shows “in process”. CPU usage shows 50% (this is the only thing the machine is doing). Perhaps a Tech will let me know if they want me to leave it alone or abort it. BETA_ E200495_ 999_ A.24.C21H16OSSi.15.4.set1d06_ 1— Pentium D (2 core), 3.00 GHz, XP SP3 32-bit, 4 gig RAM, BOINC 6.10.58 Did a bit of testing. Shut down and restarted BOINC (LAIM on) and it came back in same state. Shut down and restarted BOINC (LAIM off) and it came back at 2:05 hours (was 15+ hours), 1.667% (was 20+%) and 21+ hours to complete and increasing. Booted the machine and it came back in same state as LAIM off. Normal restart message. I will wait until I hear from Tech's or it runs past 12 hours. Unless Tech's want me to keep it going, if it goes past 12 this time I'll abort it. It's a long time since I had one this strange.  FWIW, after the restart yesterday this wu appears to have resumed normal (to use the word loosely) processing albeit very slow. It is now at 24 hours, 65% complete and the 13 hour "to completion" is dropping at a rate of 4 seconds/second. If this continues it should complete in 3-4 hours. Looks like what ever the problem was (is) is on my end or some checkpoint issue. It will be interesting to see what is granted for this marathon.  I will glad to see it end as I have my copy of Diskkill ready!! Then it is off to recycling for this old cruncher.  Runtimes, bandwidth and checkpointing are going to be problematic for some on this project.   |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Hyperthread run time comparison. One of my boxes has 8 cores and is hyperthreaded so it normally runs 16 jobs at a time. When the clean energy beta jobs were released yesterday, the box downloaded 8 beta jobs. I manipulated tha queue so that all 8 energy jobs ran at the same time along with 8 c4cw jobs. All jobs completed normally. The energy jobs ran 10-12 hours. The box downloaded another 8 clean energy beta jobs. I set the max cpu's to 8 (50% of available) and manipulated the queue so that the box would run 4 energy jobs along with 4 c4cw jobs for a total of 8 jobs. All jobs completed normally. The energy jobs ran in 6-7 hours. There may or may not be any correllation in run times to cores used. FWIW I've had WUs take anywhere from 5 to 12 hours on the same HT box @ 100%. 
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.
----------------------------------------  [Edit 1 times, last edit by nanoprobe at Sep 23, 2010 3:50:30 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Hi DM,
----------------------------------------plz make a screenshot of the Task Properties and I might be able to tell you. Please tell me with that what the normal hourly claim is for that client or the 2 benchmark values and I can share with you what the grant will be by close approximation... meantime look if your wingman already checked in. (secretly, for all I can make out you are reporting Elapsed time and TTC in 6.10.58 is projected Elapsed time *remaining* too on running jobs)
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges:
|
Hi DM, plz make a screenshot of the Task Properties and I might be able to tell you. Please tell me with that what the normal hourly claim is for that client or the 2 benchmark values and I can share with you what the grant will be by close approximation... meantime look if your wingman already checked in. (secretly, for all I can make out you are reporting Elapsed time and TTC in 6.10.58 is projected Elapsed time *remaining* too on running jobs) Hi Sek, Thanks for the kind offer but this machine will be dead today and I really don't care. The wingman still shows "in process".All of my farm is now i7 920's and they finished all beta's prefectly. It was an accident on my part that let this machine get a wu. It is a beautiful day here and I need to get outside and get to work.  Thanks again! |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges:
|
I am proud (
---------------------------------------- ) to announce it finally ended after 28:30:34 hours (+13 hours lost in the checkpoint restart). It did stop at exactly 12 hours CPU time. Why it took this machine 28 ½ hours to do 12 CPU hours work when it was doing nothing else will remain a mystery. It was a good cruncher for years. It was its last wu though. My wingman is still MIA so I don’t know about credit. I’m sure it’s not enough.  I am about to insert the “lobotomy disk” in this machine and am having flashbacks to HAL in the movie “2001” … Daisy, daaiissyy, daaiiiii …………  |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2977 Status: Offline Project Badges: 
|
RIP to your old stalwart - at least it contributed to the advancement of science in it's "quieter moments" (which, unfortunately, is something that can't be said for the vast majority of computers just sitting, idling...)
---------------------------------------- |
||
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges:
|
RIP to your old stalwart - at least it contributed to the advancement of science in it's "quieter moments" (which, unfortunately, is something that can't be said for the vast majority of computers just sitting, idling...) Well said gb009761. Like with an old pet, it is a sad moment but you know it is time to do it. Actually it will go to my local school district where some 8-yo will have to do his/her homework on it. Cheers!  |
||
|
|
|