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: 26
Posts: 26   Pages: 3   [ Previous Page | 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2655 times and has 25 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Oddity in BOINC Credit

1. CPU Benchmarks for this machine are:
1/24/2008 10:57:44 AM||Running CPU benchmarks
1/24/2008 10:58:15 AM||Benchmark results:
1/24/2008 10:58:15 AM|| Number of CPUs: 2
1/24/2008 10:58:15 AM|| 2619 floating point MIPS (Whetstone) per CPU
1/24/2008 10:58:15 AM|| 5829 integer MIPS (Dhrystone) per CPU
2. Yes, HCC exclusively
3. I haven't but I just did. I'm seeing it at 0 for the HCC tasks, then about every 5 seconds it spikes to 131 and then to 0. I don't know if that's unusually high or not.

Thanks.
[Jan 24, 2008 4:01:42 PM]   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: Oddity in BOINC Credit

Hello billroland,
I can't think of anything off the top of my head. So . . . that means I need more information to see if that gives me an idea.

Could you copy the message tab in BOINC from boot through download and sending back a completed work unit? Then add the information from your Results Status page for that work unit.

Lawrence
I'll be happy to get that info for you. I just restarted BOINC prior to reading your post so when I have some data I'll post it up. Thanks.
[Jan 24, 2008 4:05:12 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: Oddity in BOINC Credit

Cloning 'old' setups could have had the nasty effect of the Device record at WCG still thinking that the old machine is on-line. Effective last week a new mechanism was put in place to *not* create a new device if certain conditions were met including the CPU, so tell us what the old CPU and benchmarks were.

Example. If the old machine did a job in 8 hours and the new in 2, the 'claim' could be calculated as against the historic values per second. Maybe if you tell us the device ID (a number in the startup log of BOINC), one of the techs could look it up. Mind you the mechanism should have corrected itself, but seemingly not here.

If you had not hidden your devices in your profile, you could in fact see in places like BOINCstats as what the device is being communicated as (there it does show hidden presently). WCG does not show this in local device pages.

wild guess.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Jan 24, 2008 4:13:04 PM]   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: Oddity in BOINC Credit

Sekerob, that was my first thought, too.

But it is claimed credit that is off the wall, not the granted credit.
[Jan 24, 2008 4:24:16 PM]   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: Oddity in BOINC Credit

Cloning 'old' setups could have had the nasty effect of the Device record at WCG still thinking that the old machine is on-line. Effective last week a new mechanism was put in place to *not* create a new device if certain conditions were met including the CPU, so tell us what the old CPU and benchmarks were.

Example. If the old machine did a job in 8 hours and the new in 2, the 'claim' could be calculated as against the historic values per second. Maybe if you tell us the device ID (a number in the startup log of BOINC), one of the techs could look it up. Mind you the mechanism should have corrected itself, but seemingly not here.

If you had not hidden your devices in your profile, you could in fact see in places like BOINCstats as what the device is being communicated as (there it does show hidden presently). WCG does not show this in local device pages.

wild guess.
The old CPU was a Pentium 4 1.3GHz, the new CPU is a Core 2 Duo 2.66GHz. I wouldn't have the slightest idea what the old benchmarks were but I can fathom a guess they were far lower than the Core 2 Duo is reporting now.

I wasn't aware I was hiding any devices nor do I really know what BOINCStats is but I think I found the option to unhide it in the WCG profile editor, so maybe that will help.
[Jan 24, 2008 8:27:16 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: Oddity in BOINC Credit

okay, the www.boincstats.com and other external boinc statistics keepers will show it with the next update. With 10,000 credit in the last day, it must be a few or? I keep them hidden though and you telling what they were, no need to unhide.

The P4-1.3 v C2D 2.66 is close to 5 times the power is my guess.

What is written in the client_state.xml file <p_model> line? The start up log of BOINC should tell the same thing what kind of CPU it thinks it is.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Jan 24, 2008 8:39:55 PM]
[Jan 24, 2008 8:37:17 PM]   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: Oddity in BOINC Credit

What is written in the client_state.xml <p_model> line? The start up log of BOINC should tell the same thing.

<p_model>Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz [x86 Family 6 Model 15 Stepping 11]</p_model>
[Jan 24, 2008 8:39:30 PM]   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: Oddity in BOINC Credit

Hello billroland,
I can't think of anything off the top of my head. So . . . that means I need more information to see if that gives me an idea.

Could you copy the message tab in BOINC from boot through download and sending back a completed work unit? Then add the information from your Results Status page for that work unit.

Lawrence

1/24/2008 11:02:54 AM||Starting BOINC client version 5.10.39 for windows_intelx86
1/24/2008 11:02:54 AM||log flags: task, file_xfer, sched_ops
1/24/2008 11:02:54 AM||Libraries: libcurl/7.17.1 OpenSSL/0.9.8e zlib/1.2.3
1/24/2008 11:02:54 AM||Executing as a daemon
1/24/2008 11:02:54 AM||Data directory: C:\BOINC
1/24/2008 11:02:55 AM||Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz [x86 Family 6 Model 15 Stepping 11]
1/24/2008 11:02:55 AM||Processor features: fpu tsc pae nx sse sse2 pni mmx
1/24/2008 11:02:55 AM||OS: Microsoft Windows Vista: Professional Edition, (06.00.6000.00)
1/24/2008 11:02:55 AM||Memory: 1.98 GB physical, 4.18 GB virtual
1/24/2008 11:02:55 AM||Disk: 149.05 GB total, 129.68 GB free
1/24/2008 11:02:55 AM||Local time is UTC -5 hours
1/24/2008 11:02:55 AM||Version change (5.10.38 -> 5.10.39)
1/24/2008 11:02:55 AM|World Community Grid|URL: http://www.worldcommunitygrid.org/; Computer ID: 211198; location: school; project prefs: school
1/24/2008 11:02:55 AM||General prefs: from World Community Grid (last modified 07-Nov-2007 18:07:02)
1/24/2008 11:02:55 AM||Host location: school
1/24/2008 11:02:55 AM||General prefs: using separate prefs for school
1/24/2008 11:02:55 AM||Reading preferences override file
1/24/2008 11:02:55 AM||Preferences limit memory usage when active to 1826.12MB
1/24/2008 11:02:55 AM||Preferences limit memory usage when idle to 1826.12MB
1/24/2008 11:02:55 AM||Preferences limit disk usage to 3.73GB
1/24/2008 11:02:55 AM||Running CPU benchmarks
1/24/2008 11:03:26 AM||Benchmark results:
1/24/2008 11:03:26 AM|| Number of CPUs: 2
1/24/2008 11:03:26 AM|| 2592 floating point MIPS (Whetstone) per CPU
1/24/2008 11:03:26 AM|| 5791 integer MIPS (Dhrystone) per CPU
1/24/2008 11:08:44 AM|World Community Grid|Restarting task X0000046720535200502241620_1 using hcc1 version 515
1/24/2008 11:08:44 AM|World Community Grid|Restarting task X0000046721190200502241610_1 using hcc1 version 515
1/24/2008 11:22:19 AM|World Community Grid|Computation for task X0000046721190200502241610_1 finished
1/24/2008 11:22:19 AM|World Community Grid|Starting X0000047020330200502101738_0
1/24/2008 11:22:19 AM|World Community Grid|Starting task X0000047020330200502101738_0 using hcc1 version 515
1/24/2008 11:22:22 AM|World Community Grid|Started upload of X0000046721190200502241610_1_0
1/24/2008 11:22:29 AM|World Community Grid|Finished upload of X0000046721190200502241610_1_0
1/24/2008 11:22:33 AM|World Community Grid|Computation for task X0000046720535200502241620_1 finished
1/24/2008 11:22:33 AM|World Community Grid|Starting X0000047020492200502101735_1
1/24/2008 11:22:33 AM|World Community Grid|Starting task X0000047020492200502101735_1 using hcc1 version 515
1/24/2008 11:22:36 AM|World Community Grid|Started upload of X0000046720535200502241620_1_0
1/24/2008 11:22:41 AM|World Community Grid|Finished upload of X0000046720535200502241620_1_0
1/24/2008 12:23:28 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 40 seconds of work, reporting 2 completed tasks
1/24/2008 12:23:33 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 12:23:36 PM|World Community Grid|Started download of X0000047021472200503031726_X0000047021472200503031726.jp2
1/24/2008 12:23:39 PM|World Community Grid|Finished download of X0000047021472200503031726_X0000047021472200503031726.jp2
1/24/2008 12:25:07 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 255 seconds of work, reporting 0 completed tasks
1/24/2008 12:25:12 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 12:25:15 PM|World Community Grid|Started download of X0000047030101200502031101_X0000047030101200502031101.jp2
1/24/2008 12:25:18 PM|World Community Grid|Finished download of X0000047030101200502031101_X0000047030101200502031101.jp2
1/24/2008 2:25:10 PM|World Community Grid|Computation for task X0000047020492200502101735_1 finished
1/24/2008 2:25:10 PM|World Community Grid|Starting X0000047021472200503031726_0
1/24/2008 2:25:10 PM|World Community Grid|Starting task X0000047021472200503031726_0 using hcc1 version 515
1/24/2008 2:25:12 PM|World Community Grid|Started upload of X0000047020492200502101735_1_0
1/24/2008 2:25:19 PM|World Community Grid|Finished upload of X0000047020492200502101735_1_0
1/24/2008 2:25:22 PM|World Community Grid|Computation for task X0000047020330200502101738_0 finished
1/24/2008 2:25:22 PM|World Community Grid|Starting X0000047030101200502031101_0
1/24/2008 2:25:22 PM|World Community Grid|Starting task X0000047030101200502031101_0 using hcc1 version 515
1/24/2008 2:25:24 PM|World Community Grid|Started upload of X0000047020330200502101738_0_0
1/24/2008 2:25:32 PM|World Community Grid|Finished upload of X0000047020330200502101738_0_0
1/24/2008 3:33:21 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 332 seconds of work, reporting 2 completed tasks
1/24/2008 3:33:26 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 3:33:29 PM|World Community Grid|Started download of X0000047030678200502101759_X0000047030678200502101759.jp2
1/24/2008 3:33:32 PM|World Community Grid|Finished download of X0000047030678200502101759_X0000047030678200502101759.jp2
1/24/2008 3:35:00 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 218 seconds of work, reporting 0 completed tasks
1/24/2008 3:35:05 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 3:35:08 PM|World Community Grid|Started download of X0000047030898200502101755_X0000047030898200502101755.jp2
1/24/2008 3:35:11 PM|World Community Grid|Finished download of X0000047030898200502101755_X0000047030898200502101755.jp2
1/24/2008 5:44:51 PM|World Community Grid|Computation for task X0000047030101200502031101_0 finished
1/24/2008 5:44:51 PM|World Community Grid|Starting X0000047030678200502101759_1
1/24/2008 5:44:51 PM|World Community Grid|Starting task X0000047030678200502101759_1 using hcc1 version 515
1/24/2008 5:44:54 PM|World Community Grid|Started upload of X0000047030101200502031101_0_0
1/24/2008 5:45:01 PM|World Community Grid|Finished upload of X0000047030101200502031101_0_0
1/24/2008 5:45:45 PM|World Community Grid|Computation for task X0000047021472200503031726_0 finished
1/24/2008 5:45:45 PM|World Community Grid|Starting X0000047030898200502101755_1
1/24/2008 5:45:45 PM|World Community Grid|Starting task X0000047030898200502101755_1 using hcc1 version 515
1/24/2008 5:45:48 PM|World Community Grid|Started upload of X0000047021472200503031726_0_0
1/24/2008 5:45:53 PM|World Community Grid|Finished upload of X0000047021472200503031726_0_0
1/24/2008 6:46:47 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 12 seconds of work, reporting 2 completed tasks
1/24/2008 6:46:52 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 6:46:55 PM|World Community Grid|Started download of X0000047030680200502242136_X0000047030680200502242136.jp2
1/24/2008 6:46:58 PM|World Community Grid|Finished download of X0000047030680200502242136_X0000047030680200502242136.jp2
1/24/2008 6:48:26 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 344 seconds of work, reporting 0 completed tasks
1/24/2008 6:48:31 PM|World Community Grid|Scheduler request succeeded: got 1 new tasks
1/24/2008 6:48:33 PM|World Community Grid|Started download of X0000047030663200502242137_X0000047030663200502242137.jp2
1/24/2008 6:48:36 PM|World Community Grid|Finished download of X0000047030663200502242137_X0000047030663200502242137.jp2
1/24/2008 8:51:53 PM|World Community Grid|Computation for task X0000047030898200502101755_1 finished
1/24/2008 8:51:53 PM|World Community Grid|Starting X0000047030680200502242136_0
1/24/2008 8:51:53 PM|World Community Grid|Starting task X0000047030680200502242136_0 using hcc1 version 515
1/24/2008 8:51:56 PM|World Community Grid|Started upload of X0000047030898200502101755_1_0
1/24/2008 8:52:01 PM|World Community Grid|Finished upload of X0000047030898200502101755_1_0
1/24/2008 8:52:51 PM|World Community Grid|Computation for task X0000047030678200502101759_1 finished
1/24/2008 8:52:51 PM|World Community Grid|Starting X0000047030663200502242137_0
1/24/2008 8:52:51 PM|World Community Grid|Starting task X0000047030663200502242137_0 using hcc1 version 515
1/24/2008 8:52:54 PM|World Community Grid|Started upload of X0000047030678200502101759_1_0
1/24/2008 8:53:00 PM|World Community Grid|Finished upload of X0000047030678200502101759_1_0
[Jan 25, 2008 2:53:29 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: Oddity in BOINC Credit

We can't troubleshoot alpha problems. If you use a test version of BOINC, you have to get support from the BOINC folks.
[Jan 25, 2008 9:06:52 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: Oddity in BOINC Credit

Hello billroland,
Looking at your times just emphasizes how old and slow my computer is. You ought to be claiming about 17.5 to 17.6 BOINC credits per hour of CPU time. If you are not, then the problem is probably on the server, adjusting your claims to match historical performance. Sekerob intends to ask the staff to look at this.

Lawrence
----------------------------------------
[Edit 2 times, last edit by Former Member at Jan 25, 2008 1:26:39 PM]
[Jan 25, 2008 9:44:40 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 26   Pages: 3   [ Previous Page | 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread