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

[halken <halken@comcast.net>]

Hi Kostas...

Yes with a full feed of spots and RBN.  It has been a long time however, 
since I ran those straight into WL.  I use CC-User to log into a cluster 
node and I use that as a front end to set up filters and buffering.  
CC-User will output spots on 127.0.0 Port #? (I forget) which WL can 
take in.  CC-User has a check box to smooth out and throttle the rate of 
spots coming across the network.  I never notice any slowness to the 
spots coming in, but there may be a few seconds delay here and there as 
the smoothing takes place.
73,
Hal N4GG


On 12/6/2015 1:37 PM, Kostas SV1DPI wrote:
> 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/