开云体育

CPU Usage

Jerry Buxton N0JY All Messages By This Member #160 Has anyone any input on the CPU usage of the D-RATS application, mine starts out all happy but after some time (appears to be a few hours, I haven't actually clocked it yet) it gets up to just over 25% CPU usage according to Task Manager. All the while it is apparently sitting idle, having received a few QSTs and sent a few QSTs, perhaps logged a couple of station locations. I restart it and everything is fine for a while again but that is no way to have to use an application, of course. Your insight is appreciated. 73 Jerry N0JY
John E. Malmberg All Messages By This Member #161 On 8/23/2013 8:57 AM, n0jy wrote: Has anyone any input on the CPU usage of the D-RATS application, mine starts out all happy but after some time (appears to be a few hours, I haven't actually clocked it yet) It is a known bug. If the connection to a ratflector is lost for any reason, d-rats goes into this CPU loop condition. Sometimes this is caused by a network provider killing idle sessions, in which case setting up a beacon every few minutes will hide this bug. Regards, -John
Jerry Buxton N0JY All Messages By This Member #162 开云体育 Thanks, John.? I am constantly connected via ID-1 to the local DD repeater, but apparently there's not enough traffic to keep it alive.? I will try setting up a do nothing ping every few minutes. Maybe checking the email every two minutes? Jerry On 8/23/2013 5:13 PM, John E. Malmberg wrote: toggle quoted message Show quoted text ? On 8/23/2013 8:57 AM, n0jy wrote: > Has anyone any input on the CPU usage of the D-RATS application, mine > starts out all happy but after some time (appears to be a few hours, I > haven't actually clocked it yet) It is a known bug. If the connection to a ratflector is lost for any reason, d-rats goes into this CPU loop condition. Sometimes this is caused by a network provider killing idle sessions, in which case setting up a beacon every few minutes will hide this bug. Regards, -John
Patrick Connor All Messages By This Member #163 I send a GPS report every 10 minutes to keep my connection alive. It keeps the loop from starting and doesn't print any text on the chat screen. Patrick toggle quoted message Show quoted text From: n0jy To: d-rats_group@... Sent: Friday, August 23, 2013 7:04 PM Subject: Re: [d-rats_group] CPU Usage ? Thanks, John.? I am constantly connected via ID-1 to the local DD repeater, but apparently there's not enough traffic to keep it alive.? I will try setting up a do nothing ping every few minutes. Maybe checking the email every two minutes? Jerry On 8/23/2013 5:13 PM, John E. Malmberg wrote: ? On 8/23/2013 8:57 AM, n0jy wrote: > Has anyone any input on the CPU usage of the D-RATS application, mine > starts out all happy but after some time (appears to be a few hours, I > haven't actually clocked it yet) It is a known bug. If the connection to a ratflector is lost for any reason, d-rats goes into this CPU loop condition. Sometimes this is caused by a network provider killing idle sessions, in which case setting up a beacon every few minutes will hide this bug. Regards, -John
Jerry Buxton N0JY All Messages By This Member #164 开云体育 Thanks Patrick.? You have that set up in the QST? It looks like the email check isn't doing any good. Jerry On 8/23/2013 8:02 PM, Patrick Connor wrote: toggle quoted message Show quoted text ? I send a GPS report every 10 minutes to keep my connection alive. It keeps the loop from starting and doesn't print any text on the chat screen. Patrick From: n0jy To: d-rats_group@... Sent: Friday, August 23, 2013 7:04 PM Subject: Re: [d-rats_group] CPU Usage ? Thanks, John.? I am constantly connected via ID-1 to the local DD repeater, but apparently there's not enough traffic to keep it alive.? I will try setting up a do nothing ping every few minutes. Maybe checking the email every two minutes? Jerry On 8/23/2013 5:13 PM, John E. Malmberg wrote: ? On 8/23/2013 8:57 AM, n0jy wrote: > Has anyone any input on the CPU usage of the D-RATS application, mine > starts out all happy but after some time (appears to be a few hours, I > haven't actually clocked it yet) It is a known bug. If the connection to a ratflector is lost for any reason, d-rats goes into this CPU loop condition. Sometimes this is caused by a network provider killing idle sessions, in which case setting up a beacon every few minutes will hide this bug. Regards, -John

Previous Topic Next Topic