| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Fight Childhood Cancer Project Forum
Thread: HFCC tasks so much slower on Vista than on XP? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Good Morning,
i´ve two laptops runnig BOINC 6.6.36. One Acer with an Intel P8400 (2.26 GHz) CPU and (unfortunately) Vista and one Dell with an Intel T7700 (2.4 GHz) CPU and XP prof. I run severall projects and each of this projects run on the Vista Notebook aprox. 10-15% longer. This is quite okay because of the slower CPU and the (maybe) Vista-Overhead. But the HFCC project is really strange because nearly each of the HFCC tasks run on my Vista notebook nearly double the time which is needed on the XP pro Notebook. So it makes no sense to run HFCC tasks on this notebook... :-( Is this a general HFCC/Vista issue or could it be something special? There are similar background processes on both machines and no other background-software on the Vista Notebook. Both machines have the same BOINC settings (incl. 80% for CPU). And I talk about the effective CPU time... (It is interesting that I get tnearly the same credit for both tasks - only 10% less on the XP pro Notebook) Here is an example of the result-log of the slow VISTA Notebook - this one took 13.26 hours of CPU-time: HFCC_ t1_ 01919789_ TrkB_ 0001_ 0-- <core_client_version>6.6.36</core_client_version> <![CDATA[ <stderr_txt> Failed to get VersionInfo size: 2 INFO:[19:52:07] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[19:53:30] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 0) _maxGenSeenSoFar changed: 2500 _maxGenSeenSoFar changed: 2626 _maxGenSeenSoFar changed: 2758 _maxGenSeenSoFar changed: 2896 _maxGenSeenSoFar changed: 3041 _maxGenSeenSoFar changed: 3194 _maxGenSeenSoFar changed: 3354 _maxGenSeenSoFar changed: 3522 _maxGenSeenSoFar changed: 3699 _maxGenSeenSoFar changed: 3885 _maxGenSeenSoFar changed: 4080 _maxGenSeenSoFar changed: 4285 _maxGenSeenSoFar changed: 4500 _maxGenSeenSoFar changed: 4726 _maxGenSeenSoFar changed: 4963 _maxGenSeenSoFar changed: 5212 _maxGenSeenSoFar changed: 5473 _maxGenSeenSoFar changed: 5747 _maxGenSeenSoFar changed: 6035 _maxGenSeenSoFar changed: 6337 _maxGenSeenSoFar changed: 6654 _maxGenSeenSoFar changed: 6987 _maxGenSeenSoFar changed: 7337 _maxGenSeenSoFar changed: 7704 _maxGenSeenSoFar changed: 8090 _maxGenSeenSoFar changed: 8495 _maxGenSeenSoFar changed: 8920 _maxGenSeenSoFar changed: 9367 _maxGenSeenSoFar changed: 9836 _maxGenSeenSoFar changed: 10328 Updating Best Energy for WU: 0.00 Finished Docking number 0 Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -8.640810 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 1) Updating Best Energy for WU: -8.64 Finished Docking number 1 Updating Best Energy for WU: -9.15 Finished Docking number 2 Updating Best Energy for WU: -9.28 Finished Docking number 3 Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -9.984890 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 4) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -9.984890 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 4) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -9.984890 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 4) Finished Docking number 4 Updating Best Energy for WU: -9.98 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Finished Docking number 8 Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -10.084200 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 13) Failed to get VersionInfo size: 2 Restoring grahics. bestEnergy: -10.084200 maxGenSeen: 10328 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 13) Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Finished Docking number 16 Finished Docking number 17 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[04:05:44] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[04:07:50] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 18) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ called boinc_finish </stderr_txt> ]]> And here´s the last one from my XP pro Notebook (which took only 5.25 hours CPU time: HFCC_ t1_ 02012052_ TrkB_ 0003_ 0-- <core_client_version>6.6.36</core_client_version> <![CDATA[ <stderr_txt> Failed to get VersionInfo size: 1812 INFO:[12:20:21] Start AutoGrid... Failed to get VersionInfo size: 1812 INFO:[12:23:26] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[12:24:03] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 10000 About to enter main loop...(dockings already completed: 0) _maxGenSeenSoFar changed: 2500 _maxGenSeenSoFar changed: 2626 _maxGenSeenSoFar changed: 2758 _maxGenSeenSoFar changed: 2896 _maxGenSeenSoFar changed: 3041 _maxGenSeenSoFar changed: 3194 _maxGenSeenSoFar changed: 3354 _maxGenSeenSoFar changed: 3522 _maxGenSeenSoFar changed: 3699 _maxGenSeenSoFar changed: 3885 _maxGenSeenSoFar changed: 4080 _maxGenSeenSoFar changed: 4285 _maxGenSeenSoFar changed: 4500 _maxGenSeenSoFar changed: 4726 _maxGenSeenSoFar changed: 4963 _maxGenSeenSoFar changed: 5212 _maxGenSeenSoFar changed: 5473 _maxGenSeenSoFar changed: 5747 _maxGenSeenSoFar changed: 6035 _maxGenSeenSoFar changed: 6337 _maxGenSeenSoFar changed: 6654 _maxGenSeenSoFar changed: 6987 _maxGenSeenSoFar changed: 7337 _maxGenSeenSoFar changed: 7704 _maxGenSeenSoFar changed: 8090 _maxGenSeenSoFar changed: 8495 _maxGenSeenSoFar changed: 8920 _maxGenSeenSoFar changed: 9367 _maxGenSeenSoFar changed: 9836 _maxGenSeenSoFar changed: 10328 Updating Best Energy for WU: 0.00 Finished Docking number 0 Updating Best Energy for WU: -8.38 Finished Docking number 1 Finished Docking number 2 Finished Docking number 3 Updating Best Energy for WU: -9.43 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Finished Docking number 8 Updating Best Energy for WU: -9.61 Finished Docking number 9 Updating Best Energy for WU: -9.67 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Finished Docking number 16 Finished Docking number 17 Finished Docking number 18 Finished Docking number 19 Finished Docking number 20 Finished Docking number 21 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ INFO:[21:20:42] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[21:21:53] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 22) Finished Docking number 0 ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ called boinc_finish </stderr_txt> ]]> Best regards, Oliver |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Forget about 6.6.36 - 6.6.38. They've got major timekeeping record issues and screw up the scheduler big time. Go back to 6.2.28, what WCG recommends as the stable version **
----------------------------------------Never noticed HFCC to actually report longer CPU times on the Result Status page unless for real hardware performance differentials. Since you run laptops, could be their [temp] throttle functions that cause the difference. ** For GPU crunchers there is no option as they need a coprocessor enabled version of BOINC... but are there actually people that do GPU crunching on laptops?
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Sep 8, 2009 7:20:35 AM] |
||
|
|
|