Also check to see if you an automatic back up running in the background.
That slows things down for me when it starts up on its own..
Alan, K7ACZ
-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of halken
Sent: Saturday, December 5, 2015 3:14 PM
To: writelog@contesting.com
Subject: [WriteLog] SCP slowdown
Hi Ron and Tom,
I'm running approx the same setup as Tom, although the OS is WIN 7. I've
done testing with 14K QSO logs, SCP, 6K callsign prefill files and SO2R and
had no bog-down, that includes while the PC was running NA3P at its highest
resolution (spectrum analyzer - a big CPU user).
Bog-downs seem to happen either from low memory as Tom suggests, or things
running in the background - which can hog CPU and/or memory. I have all the
auto-update stuff on the PC turned OFF.
The logging computer here only logs and supports the rigs. It never goes on
the internet or does other functions. I transfer update files to it over a
local network. Never, ever, running a browser on a PC can do wonders for
performance...
73,
Hal N4GG
On 12/5/2015 5:45 PM, Tom Georgens wrote:
Hi Ron
I am running a Lenovo X200, 2.4 GHz, 3GB, laptop running XP. I had a
comparable number of QSO's and did not notice any material slowdown.
The CPU was also acting as a DVK and running custom wattmeter and
station control software using 8 com ports.
If it is the machine, I suspect it will be more about the memory than
the CPU speed.
FWIW, I do see Writelog slow down occasionally. Usually if you stop
and restart Writelog a bunch of times, it seems to slow down. This is
especially true after it crashes. A CPU restart generally restores it to
normal. Also, if it is having network trouble, the performance will lag.
73
Tom W2SC 8P5A
-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of
Ron Dohmen
Sent: Saturday, December 05, 2015 10:01 AM
To: WriteLog@contesting.com
Subject: [WriteLog] Super Check Partial Slowing Down for big Logs
At our recent PZ5W operation we noticed the Super check partial window
slowing down as the log got larger and larger. It was quite
noticeable at
8,000 QSOs, and almost unusable at 10,000 QSOs. When we logged more
than
10,000 QSOs, the report had already been transmitted before the window
populated. Nothing else slowed down, just the Super check partial
window.
Is there any way to speed up the super check partial function? We were
using a Lenovo Laptop with a quad core i5-4210U 1.70 GHz CPU. Should have
been enough horsepower. Is there any way to dedicate one of the
processors
to the super check partial function?
73 de Ron N0AT
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/