I have definitely seen the WL SCP process slow down on big logs. In the 2014
CQWW SSB once I got above ~5,000 QSOs in the log the SCP window would not
update until I was ready to log the QSO. This is with a i5-3317 (1.7 GHz),
4GB of RAM, and a 160GB SSD drive -- I was not running packet and only had a
microKeyer II connected to the laptop. The same thing happened again this
year. A few things I have learned and conjecture:
* By the time you get to these types of QSO counts the % of calls in the SCP
drops off dramatically. SCP can still be helpful, I usually try to double
check any call that does not show up in SCP, but at some point doing so
slows your rate down so much you just have to trust yourself.
* It will probably help to use as small a .DTA as you can. If you are in the
US during CQWW or ARRL DX don't use the full MASTER.DTA, use MASTERDX.DTA.
Similarly if you are outside the US in ARRL DX, don't use MASTER.DTA, use
MASUSVE.DTA, etc.
* I have heard that turning off "Set for Automatic Rescoring" can free up
CPU cycles for other WriteLog processes but, at least in CQWW this does not
seem to help SCP speed.
* I also suspect contest to contest variation can be caused by the contest
module. For example the W7 QSO party module bogged down PC's so bad that it
made WriteLog essentially unusable -- CW sending was jittery, logging
lagged, etc. And this was with zero QSOs in the log. In that case turning
off Automatic Rescoring did seem to help for a short period. But after
suffering through it for one year we moved to N1MM.
And congrats to Tom, 8P5A. I thought I had a pretty good overall QSO count
in CQWW SSB. I should be in the top five worldwide. Then I realized that for
every 2 QSOs I made -- Tom made 3. Mindboggling.
Scott/YN5Z/K7ZO
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|