[Skimmertalk] Several hams experiencing major CWS slow down

Wed Jul 29 12:54:16 EDT 2020

I added a bandplan that omits FT# segments. This does work and reduces the number of decoders by about 50 in current conditions on 20m. The number could of course run higher, but seems it would have to be in the hundreds to affect performance.

If this does turn out to be the source of the slowdown a new version of bandplan.ini should solve the problem. But at the moment I’m guessing the problem is something else.

Ed / w2rf

From: Andrew O'Brien <k3ukandy at gmail.com> 
Sent: Wednesday, July 29, 2020 9:38 AM
To: E.H. Russell <ehr at qrv.com>
Cc: N4ZR <n4zr at comcast.net>; SkimmerTalk Reflector <skimmertalk at contesting.com>
Subject: Re: [Skimmertalk] Several hams experiencing major CWS slow down

One ham experiencing this issue reports that the problem has been fixed by reverting back to CWS 2.0 rather than. 2.1. I will experiment some more , I edited bandplan.ini over night and set to CW 7000 to 7060  and it is handling the 120 or so decoders well this morning . 

I still wonder about video driver issues . 

Andy K3UK 

On Jul 29, 2020, at 7:58 AM, E.H. Russell <ehr at qrv.com <mailto:ehr at qrv.com> > wrote:

I’ve just started looking into CWS potential interaction with FT# causing a slowdown. So far:

              I can’t find a band plan that bypasses decoding FT# segments.

              Even so, there are only about 50 decoders allocated for FT#

It seems this would need to be in the hundreds before it becomes a drag on performance.

More info coming as I explore this.

Ed / w2rf

From: Skimmertalk <skimmertalk-bounces+ehr=qrv.com at contesting.com <mailto:skimmertalk-bounces+ehr=qrv.com at contesting.com> > On Behalf Of Andrew O'Brien
Sent: Tuesday, July 28, 2020 11:57 PM
To: N4ZR <n4zr at comcast.net <mailto:n4zr at comcast.net> >
Cc: SkimmerTalk Reflector <skimmertalk at contesting.com <mailto:skimmertalk at contesting.com> >
Subject: Re: [Skimmertalk] Several hams experiencing major CWS slow down

and... I'm talking about CWS, not the server. Mostly a decode slowdown and not a video driver issue.

Andy 

On Tue, Jul 28, 2020 at 11:54 PM Andrew O'Brien <k3ukandy at gmail.com <mailto:k3ukandy at gmail.com> > wrote:

The whole FT free zones issue  never even occurred to me.  I'll take a look and see if this is indeed the issue. 

The Facebook CWS page is at https://www.facebook.com/groups/cwskimmer/

Andy K3UK 

On Tue, Jul 28, 2020 at 11:51 AM N4ZR <n4zr at comcast.net <mailto:n4zr at comcast.net> > wrote:

I have implemented FT#-free zones in the band segments in my CW and RTTY ini files - helps a bunch!

73, Pete N4ZR
Check out the Reverse Beacon Network 
at  <http://reversebeacon.net> <http://reversebeacon.net>, now 
spotting RTTY activity worldwide. 
For spots, please use your favorite 
"retail" DX cluster.

On 7/28/2020 11:27 AM, Bob Wilson, N6TV wrote:

Are they using CW Skimmer or Skimmer Server?  Facebook?  Where?  They should ask here. 

Failure to exclude FT8 (and FT4?) frequencies from RTTY and CW spotting should help reduce the "decoder counts," which is the main cause of high CPU utilization.

Or by "slow down", do they mean the horizontal waterfall of CW Skimmer moves more slowly?  That sounds like a video driver issue.

73, 

Bob, N6TV

On Tue, Jul 28, 2020 at 6:21 AM Andrew O'Brien <k3ukandy at gmail.com <mailto:k3ukandy at gmail.com> > wrote:

I have seen about 5-6 recent comments on Facebook from hams successfully running CWS without problems in the past but in the last few months, they experience major "slow down" of CWS .  Does anyone know the source of this problem? The primary symptom is decoding capacity reaching 100% even in low activity days. One person said they recently increased their RAM from 8 to 16 and then to 32 gigs but the slow down still happens.  System resources reported by Windows do not indicate CPU or RAM is close to maxing out.   It cant be related to any CWS updates, so I am wondering about Windows updates. 

Andy K3UK

_______________________________________________
Skimmertalk mailing list
Skimmertalk at contesting.com <mailto:Skimmertalk at contesting.com> 
http://lists.contesting.com/mailman/listinfo/skimmertalk

_______________________________________________
Skimmertalk mailing list
Skimmertalk at contesting.com <mailto:Skimmertalk at contesting.com> 
http://lists.contesting.com/mailman/listinfo/skimmertalk

_______________________________________________
Skimmertalk mailing list
Skimmertalk at contesting.com <mailto:Skimmertalk at contesting.com> 
http://lists.contesting.com/mailman/listinfo/skimmertalk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.contesting.com/pipermail/skimmertalk/attachments/20200729/1a208cc2/attachment.html>