| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Delays when unlocking a locked session - Windows XP |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have been running the latest agent on Windows XP for a few months now.
I lock my workstation when I am not actively using it. This is done via a 10 minute Blank screensaver with "On resume, password protect" checked, or via the WinKey+L combination. The problem is when I come to unlock the session. The unlock process (show login screen, accept password, return to full desktop) is annoyingly slow. It can take up to 1 minute for the login screen to appear (moving the mouse, or CTRL-ALT_Del). I enter the password or swipe my finger. Then wait up to 3 minutes before I can do anything. During this time I can see my desktop wallpaper but nothing else. The computer is clearly still doing stuff in the background as sounds and notifications continue to play. As soon as I exit the BOINC manager and WCG processes, the delay disappears completely. The computer runs smooth and fast. The delay also seems to vary now and then - presumable depending on what the agent is doing. I am not running WCM in screensaver mode. I have not installed any other screensavers or software that can affect login. This happens regardless of whether I am on a network or not. The BOINC software appears to be the culprit. I will disable it for the time being. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm taking it that BOINC is set to 100% crunching all the time. The newest client can be set to pause when X percent of non-BOINC CPU use is detected, meaning that when you hit the mouse or keyboard and this causing loads of disk swapping (which is what I guess is happening), BOINC will pause for that user-resume period.
There's this solution "While processor usage is less than 90%" for instance and a 3rd party utility, ThreadMasterGUI. Latter I've set to never allow the science apps to take more than 98% on my not so powerful laptop with W7. The 2% is then the instantaneous headroom available to the system/user. The system responsiveness improved dramatically with that working on big data sets and simultaneous listening to the Windows Media Player memory hog or streaming radio/video Let us know, as we certainly can work to improve the situation with some tweaks. Any portion of your spare CPU time is very much appreciated. --//-- |
||
|
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: 
|
Are you running CEP by any chance? What SekeRob said makes sense, you likely have most of your real memory consumed by other tasks ... presumably WCG Science and when you come back, a whole lot of paging has to go on before you can get a big enough working set in memory for it to look and act normal. Again like SekeRob indicated, there are restrictions that you can impose on the WCG workload that would likely ease the problem a bunch. My early-on guess is memory thrasing which you can tweek in the Device Profile>Memory Usage. You might want to play with that and see what happens.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BIONC had been set to 30%.
----------------------------------------The system RAM is maxed out at 3Gb (Thinkpad T60p). The main HDD is an SSD with lots of free space. I do run a lot of apps concurrently - Adobe Photoshop/Illustrator, Office (Word, Visio) and multiple sessions in Firefox. I don't listen to music or play videos when working. What is CEP?? Thanks for the replies. I do want to help. I just don't need to troubleshoot a "non-essential" app right at this moment. I dont recall having these issues when I was using the non-BOINC app years before. The switchover to the BOINC app and the associated issues was what stopped me contributing to WCG the first time. Anyway, hope you understand. :) [Edit 1 times, last edit by zern at Feb 6, 2011 5:12:57 PM] |
||
|
|
|