Progressively slowing updates in cluster window

[WB8ICQ]

I apologize if this has been answered before but I could not find it in the forums. When I first connect to Telnet cluster, I see spots showing in the Cluster window of the main Log4OM2 screen, and when comparing with system time (which is accurate and shows current local time) the spots post within a minute or so of the time shown on the spot. As I leave Log4OM2 running, I see a progressively increasing delay between the time listed on the spot and the time it appears in the Log4OM2 main screen. After Log4OM2 has been running for about 20 minutes, spots appear with time stamps about 17 minutes behind system time. After Log4OM2 has been running about 35 minutes, the spots appear with time stamps about 23 minutes behind the system time. The longer Log4OM2 is running, the longer the delay in cluster spots appearing in the Cluster window of the main Log4OM2 screen. Meanwhile, the Cluster Management popup window shows spots scrolling by with time stamps that are the same as system time.

This has been a consistent problem over a year of Log4OM2 use, across multiple Log4OM2 updates, and on two different PCs.

Here's the current installation:
Log4OM2 version: 2.18.0.0
Log4OM2 log storage: local, on SSD in PC, with backup to thumb drive in PC.
Log4OM2 active cluster servers: K4MD, KG4V. Most of the spots are coming from KG4V.
Cluster filters: Mode lock is unchecked, but CW and phone are checked. Band lock is unchecked and no bands are selected.

System: Intel Core i5-3470, 8 Gb RAM
Windows: Windows 10 Pro, version 10.0.19044 Build 19044. Windows and all software run from the SSD.
Other software running concurrently: Firefox.

Suggestions on how to fix this will be much appreciated, and thanks!
73,
Scott WB8ICQ

[G4POP]

Scott,
I cant try the servers that you use because they seem to want me to register to them but using VE7CC and GB7MBC I have been watching the results for the last couple of hours and its working fine here without a time lag.

So have you tried some different servers just in case there is a problem with the ones your using?

[WB8ICQ]

Thanks for the response, Terry. I will give that a try. I must admit that I am not optimistic, however, that the problem is the cluster servers I am connected to. Here's my logic:

The Cluster Management popup window shows spots scrolling by with time stamps that are the same as system time. That tells me the connection between my PC and the cluster server is working as it should. That, in turn, suggests to me that the problem is somehow within my installation of Log4OM2.

I don't think the problem is due to a corrupt installation of Log4OM2. The problem has persisted on the same computer even when I update to new versions. The problem even persisted when I installed Log4OM2 on a different computer, twice: first, when I switched to a new computer and freshly installed Win10 and Log4OM2 on its hard drive, and second, when I replaced that hard drive with a SSD and created a completely new installation of Windows and Log4OM2 on the SSD. Hard to imagine the installation would corrupt every time, so I conclude Log4OM2 is correctly installed.

Given that nobody else seems to have this problem with Log4OM2, after the above chain of thought I think it most likely that I have something configured incorrectly. As best I can tell my installation conforms to the guidance in the user guide, so I must be missing something.

I'll try unselecting the current servers and selecting a different one (or more) to see what happens. In the meantime, if you have additional thoughts I'll be glad to hear them!
73,
Scott WB8ICQ

[KI5IO]

Scott,

I was able to step through the additional login prompts that the K4MD cluster requests and have been running it now for the past 2-hours.

I'm not experiencing any time slippages, delays or lags. Nor have I experienced such when I use the VE7CC cluster.

Not sure what might be causing such on your installation. I have a real old Dell laptop that I use and the processor is slow and gets bogged down when there is a special event or even a CWT as it makes the process runs it's little legs off trying to keep up, but still now time delays.

Check your "Reliability Threshold" settings on your Cluster panel windows. I find that if I have that slider moved to the right there can be a difference of spot display as I compart the cluster view from the Cluster Management Panel side by side with the Main UI cluster. Each have their own "Reliability Threshold" settings.

I keep mine typically at the far left and once I move the slider I tap the button to refresh the reliability filter.

I've also include a screen clip of my cluster settings. My Cluster Overload Control (bottom item/value) at 5 as that helps throttle a high volume of spots so that it don't overload my CPU as much during those high volume events.