[WriteLog] CPU bog down - Progress

[Gary AL9A]

Been following this thread for a while and I've not noticed the delay in 
spacing from one field to another.  I usually run with a telnet connection, 
except for those contests that don't allow spots to be used, and don't 
notice any delay, even when running CW and getting lots of skimmer spots. 
BTW, I have auto rescoring enabled.

I obviously don't know the code involved, but I seriously doubt that with 
atuomatic scoring enabled WL goes through all spots that have been received 
looking for mults.  That would be pointless.  Your score is based on the 
mults actually in the log, not those that are spotted.  There is no need to 
go through thousands of spotted mults if you only have a couple of hundred 
in the log.  That cannot be consuming much CPU time at all.  I'm perplexed 
by what might be different in our systems that causes the lag you are seeing 
that I do not see.

73,
Gary AL9A


----- Original Message ----- 
From: "Ron NØAT" <n0at at comcast.net>
To: "'Hal Kennedy'" <halken at comcast.net>; <writelog at contesting.com>
Cc: <w5xd at writelog.com>
Sent: April 17, 2011 3:33 PM
Subject: Re: [WriteLog] CPU bog down - Progress


Hal,

Thanks for the info on the Writelog slowing down problem.  I have been
struggling with this during the past two Minnesota QSO party contests.  I
tested my system and verified your suggestion to turn off automatic
rescoring completely removes the delay when hitting the spacebar to move the
cursor out of the callsign field.

When I shut off automatic scoring, a windows pops up asking if I want to
turn off the module's "Automatic checking and score summary" Automatic
multiplier checking.

It appears to me as though every time you space out of the callsign field
the software goes through all the packet spots that have been received and
checks each one of them for a new multiplier.  The software gets slower and
slower as time goes on because more packet spots have been received.  If you
shut down Writelog and restart it, everything is at full speed again, until
the packet spot buffer begins to fill up.  But turning off automatic
rescoring, or shutting off the packet window eliminates the delay.

73 de Ron NØAT


-----Original Message-----
From: writelog-bounces at contesting.com
[mailto:writelog-bounces at contesting.com] On Behalf Of Hal Kennedy
Sent: Friday, April 15, 2011 11:06
To: writelog at contesting.com
Cc: w5xd at writelog.com
Subject: [WriteLog] CPU bog down - Progress

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 at contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/


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