Screensaver slows processing

Author	Message
Thurlow Farnsworth Send message Joined: 28 May 99 Posts: 32 Credit: 16,022,409 RAC: 0	Message 113688 - Posted: 22 May 2005, 3:49:44 UTC Running ver 4.19 BOINC with XP-Home. When screensaver is running, SETI processing slows gradually to a stop. When it is running Einstein, it slows processing. I have verified this having both windows running side-by-side. Anyone else run into this? ID: 113688 ·

mikey Volunteer tester Send message Joined: 17 Dec 99 Posts: 4215 Credit: 3,474,603 RAC: 0	Message 113694 - Posted: 22 May 2005, 4:15:46 UTC Do you think that maybe, just maybe it could be because your computer is using processor time to draw all those pretty pictures? This was PROVEN long ago in Classic, that is why the CLI(Command Line Interface) version came out, no pictures but an almost 20% increase in speed. ID: 113694 ·

Thurlow Farnsworth Send message Joined: 28 May 99 Posts: 32 Credit: 16,022,409 RAC: 0	Message 113717 - Posted: 22 May 2005, 6:32:14 UTC - in response to Message 113694. Do you think that maybe, just maybe it could be because your computer is using processor time to draw all those pretty pictures? This was PROVEN long ago in Classic, that is why the CLI(Command Line Interface) version came out, no pictures but an almost 20% increase in speed. ID: 113717 ·

Thurlow Farnsworth Send message Joined: 28 May 99 Posts: 32 Credit: 16,022,409 RAC: 0	Message 113720 - Posted: 22 May 2005, 6:36:40 UTC - in response to Message 113694. Do you think that maybe, just maybe it could be because your computer is using processor time to draw all those pretty pictures? This was PROVEN long ago in Classic, that is why the CLI(Command Line Interface) version came out, no pictures but an almost 20% increase in speed. Could be, but I never saw this as problematic with the classic version. I'm running AMD Athlon 2700+ with 512mb RAM, and this happens even tho nothing else is running other than the start-up support stuff. ID: 113720 ·

mikey Volunteer tester Send message Joined: 17 Dec 99 Posts: 4215 Credit: 3,474,603 RAC: 0	Message 113802 - Posted: 22 May 2005, 16:27:04 UTC - in response to Message 113720. Last modified: 22 May 2005, 16:27:19 UTC Do you think that maybe, just maybe it could be because your computer is using processor time to draw all those pretty pictures? This was PROVEN long ago in Classic, that is why the CLI(Command Line Interface) version came out, no pictures but an almost 20% increase in speed. Could be, but I never saw this as problematic with the classic version. I'm running AMD Athlon 2700+ with 512mb RAM, and this happens even tho nothing else is running other than the start-up support stuff. Pretty pictures take cpu power to generate, they are not offloaded to the graphics card, some couldn't handle it anyway, they are done by the main cpu and takes time. ID: 113802 ·

Wingless Wonder Send message Joined: 14 May 99 Posts: 14 Credit: 12,157,146 RAC: 0	Message 114095 - Posted: 23 May 2005, 12:46:10 UTC - in response to Message 113720. Last modified: 23 May 2005, 12:47:29 UTC Origami posted by Thurlow Farnsworth [font=Arial]Could be, but I never saw this as problematic with the classic version. I'm running AMD Athlon 2700+ with 512mb RAM, and this happens even tho nothing else is running other than the start-up support stuff. [/font] There's one way to know for sure - disable the graphics display of the SETI@home screensaver by checking 'Go to blank screen' setting > minutes to go blank = 0 (zero). -- 0==WW==0 "â€¦axles of evilâ€¦" - george w. bush ID: 114095 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.