[WriteLog] Super Check Partial Slowing Down for big Logs
halken
halken at comcast.net
Mon Dec 7 19:42:11 EST 2015
For all interested in this, it's easy to make very large logs for
testing. Just open a log and then start importing more logs. I have a
few 7K QSO logs from M2 and M/M trips I have been on. I just import two
or three of those onto the end of something open. You can quickly make
a log of almost any size this way...
73
Hall N4GG
On 12/7/2015 1:05 PM, john at kk9a.com wrote:
> While I do not make 10,000 QSOs in a contest like W2SC, I have never
> noticed a slowdown. What is slow, after you log a QSO do you have to wait
> until you can log the next one or is SCP slow to display? I save my log on
> occasion during slower times and not automatically after every QSO.
>
> John KK9A
>
>
> To: <WriteLog at contesting.com>
> Subject: Re: [WriteLog] Super Check Partial Slowing Down for big Logs
> From: "Tom Georgens" <tomgeorgens15 at gmail.com>
> Date: Sat, 5 Dec 2015 14:45:49 -0800
>
> 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 at contesting.com] On Behalf Of Ron
> Dohmen
> Sent: Saturday, December 05, 2015 10:01 AM
> To: WriteLog at 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 at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
More information about the WriteLog
mailing list