Latency

[ik3umt]

If I click a cluster row, QSO area is almost immediately filled with all infos but I have to wait 5 to 7 seconds before a further click on cluster row fills again QSO area with new callsign data.
Is it a correct behavior ?
Does it depends by CPU load/capability ?

[G4POP]

Not normal check the perfomance menu in the program config

[ik3umt]

I expected quick jumps between cluster rows, but once a callsign is selected , system is like freezed for seconds....

[ik3umt]

Also on "Recent Qso" window, I double-click a qso and it opens after 7-8 seconds.....
What to check ?
Cpu is a quite old Phenom II X4 955 with 16GB ram and SSD
No issues with any other software...

[G4POP]

What OS?

[ik3umt]

Windows10 22H2

I noted that once cluster row is selected, access to other windows (Main, Recent qsos, Propagation, Worked before and Weather) is freezed too for the same amount of seconds.

[IW3HMH]

Some activities are performed but in background.
I'll check if there is something wrong

[ik3umt]

Hi Daniele,
If there aren't complains from other users, I suspect it's an issue of mine....
I'll try installation and behavior check on a Ryzen7 new laptop

[K4TOR]

Hi Daniele,
If there aren't complains from other users, I suspect it's an issue of mine....
I'll try installation and behavior check on a Ryzen7 new laptop

Just for kicks and giggles, can you try disabling VOACAP propagation in your settings, and see if it helps.

[ik3umt]

Just for kicks and giggles, can you try disabling VOACAP propagation in your settings, and see if it helps.

Bingo !
I could have done it before....
Now switch between all sections, cluster row, folders etc etc is almost immediate.
Meanwhile, i installed LOG4OM into a Ryzen7 5825 CPU Notebook with 16Gb ram, despite overall performaces are slightly better than Phenom , Voacap is a performance killer, however.

Unless a workaround is available, I'll run Voacap out of LOG4OM when needed.