Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 33
Posts: 33   Pages: 4   [ 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 8557 times and has 32 replies Next Thread
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
CEP2 Quick CPU Processing Times?

I don't have a super computer, but my CPU processing time compared to my wingman is way quicker. I've only processed 15 WU so maybe it's just a fluke. All of them have completed valid, except for one that error'd which all other wingmen did also.

I've got an IntelĀ® PentiumĀ® Processor E5300 (2M Cache, 2.60 GHz, 800 MHz FSB) dual processor and running Slackware Linux 13.1 x86.

Maybe the 1 MB per processor L2 cache is the speed demon?

Anyone else with 1.5 to 2 hour CPU processing times?

Here's some examples:

200193_ 530_ A.20.C18H13NS.35.2.set1d06_ 1-- 619 Valid 7/23/10 07:49:13 7/23/10 17:05:26 7.11
E200193_ 530_ A.20.C18H13NS.35.2.set1d06_ 0-- 619 Valid 7/23/10 07:48:12 7/23/10 18:03:59 1.52 <==== Me

E200203_ 099_ A.20.C17H15NSSi.11.set1d06_ 1-- 619 Valid 7/26/10 13:11:41 7/26/10 20:36:00 1.43 <==== Me
E200203_ 099_ A.20.C17H15NSSi.11.set1d06_ 0-- 619 Valid 7/26/10 13:09:11 7/27/10 12:53:57 12.00

E200197_ 740_ A.21.C18H11N3.126.set1d06_ 1-- 619 Valid 7/24/10 17:48:52 7/25/10 07:46:48 1.29 <==== Me
E200197_ 740_ A.21.C18H11N3.126.set1d06_ 0-- 619 Valid 7/24/10 17:47:29 7/25/10 00:28:39 5.50
----------------------------------------
[Edit 1 times, last edit by codes at Jul 27, 2010 4:41:13 PM]
[Jul 27, 2010 4:31:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

Just in case there's something corrupted with my WCG software install, I'll let the current WU's complete, then reinstall the application to see if that changes anything. I don't have confidence in the low CPU times being reported.
[Jul 28, 2010 5:37:17 PM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

codes,

Please look at your results again, and click on the word "Valid". It'll let you know how many steps your computer ran. Also, that 12 hour work unit could have been paired with an extremely slow machine. I have one that is a celeron 500 Mhz running for testing. I'm sure others have slow linux boxes as well. But look at the valid logs, if you could post what they show in the logs. No reason to reinstall unless we can see something wrong.

-Uplinger
[Jul 28, 2010 6:10:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

Here's my E200203_ 099_ A.20.C17H15NSSi.11.set1d06_ 1-- 619 Valid 7/26/10 13:11:41 7/26/10 20:36:00 1.43
my wingman says 12 for CPU Time hours that he processed it.

I don't see any errors in the "Messages" log.

It just amazes me that my processor can be that fast compared to others if those are true CPU times. Maybe time slows down at my house? smile

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[11:05:22] Number of jobs = 16
[11:05:22] Starting job 0,CPU time has been restored to 0.000000.
[11:05:22] Starting new Job
[11:05:24] Qink name = fldman
[11:05:24] Qink name = gesman
[11:05:24] Qink name = scfman
[11:06:54] Qink name = anlman
[11:06:54] End of Job
[11:06:57] Finished Job #0
[11:06:57] Starting job 1,CPU time has been restored to 61.115709.
[11:06:57] Starting new Job
[11:06:57] Qink name = fldman
[11:06:57] Qink name = gesman
[11:06:57] Qink name = scfman
[11:11:04] Qink name = anlman
[11:11:12] End of Job
[11:11:15] Finished Job #1
[11:11:15] Starting job 2,CPU time has been restored to 125.578909.
[11:11:15] Starting new Job
[11:11:15] Qink name = fldman
[11:11:15] Qink name = gesman
[11:11:15] Qink name = scfman
[11:14:04] Qink name = anlman
[11:14:04] Qink name = drvman
[11:14:54] Qink name = optman
[11:14:55] Qink name = fldman
[11:14:55] Qink name = gesman
[11:14:55] Qink name = scfman
[11:20:05] Qink name = anlman
[11:20:05] Qink name = drvman
[11:20:55] Qink name = optman
[11:20:55] Qink name = fldman
[11:20:55] Qink name = gesman
[11:20:56] Qink name = scfman
[11:25:46] Qink name = anlman
[11:25:46] Qink name = drvman
[11:26:35] Qink name = optman
[11:26:35] Qink name = fldman
[11:26:35] Qink name = gesman
[11:26:36] Qink name = scfman
[11:31:02] Qink name = anlman
[11:31:02] Qink name = drvman
[11:31:51] Qink name = optman
[11:31:51] Qink name = fldman
[11:31:51] Qink name = gesman
[11:31:51] Qink name = scfman
[11:35:54] Qink name = anlman
[11:35:54] Qink name = drvman
[11:36:43] Qink name = optman
[11:36:43] Qink name = fldman
[11:36:43] Qink name = gesman
[11:36:44] Qink name = scfman
[11:40:44] Qink name = anlman
[11:40:44] Qink name = drvman
[11:41:33] Qink name = optman
[11:41:33] Qink name = fldman
[11:41:33] Qink name = gesman
[11:41:34] Qink name = scfman
[11:45:10] Qink name = anlman
[11:45:11] Qink name = drvman
[11:45:59] Qink name = optman
[11:46:00] Qink name = fldman
[11:46:00] Qink name = gesman
[11:46:00] Qink name = scfman
[11:49:03] Qink name = anlman
[11:49:03] Qink name = drvman
[11:49:52] Qink name = optman
[11:49:52] Qink name = anlman
[11:50:00] End of Job
[11:50:03] Finished Job #2
[11:50:03] Starting job 3,CPU time has been restored to 188.796298.
[11:50:03] Starting new Job
[11:50:03] Qink name = fldman
[11:50:03] Qink name = gesman
[11:50:03] Qink name = scfman
[11:54:47] Qink name = anlman
[11:54:55] End of Job
[11:54:57] Finished Job #3
[11:54:57] Starting job 4,CPU time has been restored to 251.156817.
[11:54:58] Starting new Job
[11:54:58] Qink name = fldman
[11:54:58] Qink name = gesman
[11:54:58] Qink name = scfman
[11:58:10] Qink name = anlman
[11:58:19] End of Job
[11:58:21] Finished Job #4
[11:58:21] Starting job 5,CPU time has been restored to 314.276221.
[11:58:21] Starting new Job
[11:58:21] Qink name = fldman
[11:58:21] Qink name = gesman
[11:58:21] Qink name = scfman
[12:01:44] Qink name = anlman
[12:01:52] End of Job
[12:01:55] Finished Job #5
[12:01:55] Starting job 6,CPU time has been restored to 377.559600.
[12:01:55] Starting new Job
[12:01:55] Qink name = fldman
[12:01:55] Qink name = gesman
[12:01:55] Qink name = scfman
[12:05:09] Qink name = anlman
[12:05:17] End of Job
[12:05:19] Finished Job #6
[12:05:19] Starting job 7,CPU time has been restored to 440.662006.
[12:05:19] Starting new Job
[12:05:19] Qink name = fldman
[12:05:20] Qink name = gesman
[12:05:20] Qink name = scfman
[12:10:04] Qink name = anlman
[12:10:12] End of Job
[12:10:15] Finished Job #7
[12:10:15] Starting job 8,CPU time has been restored to 503.925388.
[12:10:15] Starting new Job
[12:10:15] Qink name = fldman
[12:10:15] Qink name = gesman
[12:10:15] Qink name = scfman
[12:13:24] Qink name = anlman
[12:13:32] End of Job
[12:13:34] Finished Job #8
[12:13:34] Starting job 9,CPU time has been restored to 567.500723.
[12:13:34] Starting new Job
[12:13:34] Qink name = fldman
[12:13:34] Qink name = gesman
[12:13:34] Qink name = scfman
[12:16:57] Qink name = anlman
[12:17:10] End of Job
[12:17:13] Finished Job #9
[12:17:13] Starting job 10,CPU time has been restored to 629.505296.
[12:17:13] Starting new Job
[12:17:13] Qink name = fldman
[12:17:13] Qink name = gesman
[12:17:13] Qink name = scfman
[12:25:23] Qink name = anlman
[12:25:37] End of Job
[12:25:39] Finished Job #10
[12:25:39] Starting job 11,CPU time has been restored to 692.857664.
[12:25:40] Starting new Job
[12:25:40] Qink name = fldman
[12:25:40] Qink name = gesman
[12:25:40] Qink name = scfman
[12:29:58] Qink name = anlman
[12:30:12] End of Job
[12:30:15] Finished Job #11
[12:30:15] Starting job 12,CPU time has been restored to 755.276174.
[12:30:15] Starting new Job
[12:30:15] Qink name = fldman
[12:30:16] Qink name = gesman
[12:30:17] Qink name = scfman
[12:52:14] Qink name = anlman
[12:54:13] End of Job
[12:54:17] Finished Job #12
[12:54:17] Starting job 13,CPU time has been restored to 819.075475.
[12:54:17] Starting new Job
[12:54:17] Qink name = fldman
[12:54:19] Qink name = gesman
[12:54:19] Qink name = scfman
[13:42:07] Qink name = anlman
[13:44:07] End of Job
[13:44:10] Finished Job #13
[13:44:10] Starting job 14,CPU time has been restored to 879.620270.
[13:44:10] Starting new Job
[13:44:11] Qink name = fldman
[13:44:12] Qink name = gesman
[13:44:12] Qink name = scfman
[14:39:52] Qink name = anlman
[14:41:52] End of Job
[14:41:54] Finished Job #14
[14:41:54] Starting job 15,CPU time has been restored to 940.975942.
[14:41:55] Starting new Job
[14:41:55] Qink name = fldman
[14:41:56] Qink name = gesman
[14:41:57] Qink name = scfman
[15:49:07] Qink name = anlman
[15:52:23] End of Job
[15:52:26] Finished Job #15
called boinc_finish
Exiting 0

</stderr_txt>
]]>
[Jul 28, 2010 8:11:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

The log says it took from 11:05 to 15:52 which is essential 4.75 hours, so I wonder how only 1.43 gets to be reported. My quad does them in about the same wallclock time but the difference with CPU time is only 10-30 minutes depending on whether the system is used or not (BOINCTasks logs both from remote)

E200202_ 578_ A.20.C17H13NSi2.11.0.set1d06_ 1-- 1292373 Pending Validation 26-7-10 09:25:53 28-7-10 17:13:08 5.24
E200199_ 593_ A.20.C12H6N4S4.1.0.set1d06_ 1-- 1292373 Valid 25-7-10 12:09:55 28-7-10 16:21:54 3.87
E200148_ 352_ A.19.C17H11NO.369.set1d06_ 2-- 1292373 Valid 25-7-10 13:37:13 28-7-10 16:21:54 4.12
E200199_ 446_ A.19.C16H13NSSe.1.2.set1d06_ 1-- 1292373 Valid 25-7-10 12:08:35 26-7-10 17:31:18 3.50
E200177_ 069_ A.20.C18H11NO.215.set1d06_ 2-- 1292373 Valid 25-7-10 11:33:30 26-7-10 10:25:36 4.54
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jul 28, 2010 8:23:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

The log says it took from 11:05 to 15:52 which is essential 4.75 hours, so I wonder how only 1.43 gets to be reported.

Hence why I'm suspicious. thinking
[Jul 28, 2010 9:09:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

Same comment as Sekerob's: my wallclock times are consistent with yours and Sekerob's, but the CPU times are more than twice yours, in the 4-hour range (with a Q6600 at 3.07 Ghz, 8 MB of L2 cache).
I am wondering if your OS is reporting CPU time correctly?

Regarding the work you are returning I don't see why it should not be good, but you might be claiming and getting half the credits you deserve, unless the BOINC benchmark is "strange" too. smile
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Jul 29, 2010 6:28:06 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

1.43h is the CPU time, the time between start and finish (4.75h) of the task is always the longer bit of time. What is your cpu time % value under preferences? if this one is low (<50%) and/or you were running other cpu-intensive tasks (anti-virus scan, gaming etc), that might explain the difference. Or maybe you use a throttling device and your cpu's are running hot...
An explanation of the slow wingmen might be that they're either running super-old linux boxes or they're running a vm.
[Jul 29, 2010 10:04:53 AM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

herna,
The problem with these CPU times is not relative to the wallclock time, it is that they are really very low for these kind of WUs. The CPU times that codes is reporting correspond to a 6 GHz processor, not to a 2.6 GHz one.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
[Jul 29, 2010 12:50:32 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 Quick CPU Processing Times?

Statistics Last Updated: 7/29/10 12:05:52 (UTC) [2 hour(s) ago]
Project Points
Generated Results Returned Total Run Time (y:d:h:m:s) Badges Earned
The Clean Energy Project - Phase 2 9,236 22 0:001:09:21:51


My last CEP2 wu completed and you can see 22 submitted for total 1 Day 9 Hr 21 Min, that would be less than 2 hours CPU time per wu. I suspect my client has under reported 4 to 5 times the actual CPU processed time. This has skewed the run time and credit for me as well as the adjusted credit granted to my wingmen. Sorry for any problems this may have caused others. Maybe the techs can adjust this by looking at the actual results submitted?

The last WU before I manually updated showed for the properties of the WU 1.17 hours for CPU Time and 5 hours for Elapsed Time. My wingman shows 3.89 CPU hours:

E200209_ 655_ A.21.C16H9NOS2Se.18.0.set1d06_ 0-- 619 Valid 7/28/10 18:04:54 7/29/10 10:59:31 1.17 18.3 / 39.1 <==== Me
E200209_ 655_ A.21.C16H9NOS2Se.18.0.set1d06_ 1-- 619 Valid 7/28/10 18:04:40 7/29/10 00:53:58 3.89 59.8 / 39.1

I built this computer 2 to 3 years ago with OEM parts. It's not overclocked and has had various flavors of Linux, BSD, and Windows operating systems installed on it. I have not seen any type of problems to date. It currently is running Slackware Linux 13.1 x86 version, no anti-virus, no games, is strickly running WCG 24/7 at 100% CPU usage.

Other than CEP2 wu's, all other WCG application wu's result in equal CPU and Elapsed time completed for the respective wu processed. So I suspect the problem is software related to CEP2 on my computer.

I plan to reset the BIOS to factory default, reinstall Linux, install the BOINC agent from the WCG site, run some more wu's. Will then see if that makes a difference.
----------------------------------------
[Edit 1 times, last edit by codes at Jul 29, 2010 3:05:39 PM]
[Jul 29, 2010 3:04:35 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 33   Pages: 4   [ 1 2 3 4 | Next Page ]
[ Jump to Last Post ]
Post new Thread