WriteLog
[Top] [All Lists]

Re: [WriteLog] Super Check Partial Slowing Down for big Logs

To: "'Kostas SV1DPI'" <sv1dpi@otenet.gr>, <writelog@contesting.com>
Subject: Re: [WriteLog] Super Check Partial Slowing Down for big Logs
From: "Tom Georgens" <tomgeorgens15@gmail.com>
Date: Mon, 7 Dec 2015 13:03:25 -0800
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Hi Kostas

I am sorry that I don't have any experience using packet with Writelog.  

Good luck

Tom

-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of Kostas 
SV1DPI
Sent: Sunday, December 06, 2015 10:37 AM
To: writelog@contesting.com
Subject: Re: [WriteLog] Super Check Partial Slowing Down for big Logs

Have you tried the same with heavy clusters spots? I always have the impression 
that clusters slow down writelog

73 Kostas SV1DPI

On 6/12/2015 12:45 πμ, 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/

_______________________________________________
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>