WriteLog
[Top] [All Lists]

[WriteLog] CPU Bogdown

To: "Writelog Reflector" <writelog@contesting.com>
Subject: [WriteLog] CPU Bogdown
From: "DickT-W0RAA" <dickt@w0raa.com>
Date: Fri, 15 Apr 2011 16:12:48 -0600
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Hal,  

How did you shut off the auto rescore?  In the INI file?  

Dick
W0RAA


>Date: Fri, 15 Apr 2011 12:05:36 -0400
>From: "Hal Kennedy" <halken@comcast.net>
>Subject: [WriteLog] CPU bog down - Progress
>To: <writelog@contesting.com>
>Cc: w5xd@writelog.com
>Message-ID: <923BE18C86BD43F2AE87F24CF442B8E2@N4GG4>
>Content-Type: text/plain; charset="us-ascii"

>Spent the morning looking at my CPU bog down issue.  The delay from
>hitting SPACEBAR and the cursor moving over can reach as much as a
>second here, and it is a function of how many spots have arrived and are
>being stored.  If I shut the tenet feed off, the program regains speed
>as spots hit 30 minutes old and get aged out.
 
>This occurs on three different computers running two different OS:  XP
>and WIN2000NTPRO, with nothing else running in the background.  The
>Windows task manager indicates WLXXXXXX.exe is pushing the CPU to 100%.
 
>Today I started shutting off WL functions that do work in the background
>every time SPACEBAR is hit.  Stopping SCP and Call Check did not help.
>Turning off "Set for automatic rescoring" completely eliminates the
>problem.  This is a relief as I can at least now use WL again.  Why the
>auto rescoring is interacting with the number of spots available I don't
>know, but maybe this will help get it fixed.  
 
>Is it possible some folks who don't see this problem have auto rescoring
>turned off?
 
>73 Hal, N4GG

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>
  • [WriteLog] CPU Bogdown, DickT-W0RAA <=