After updating to v2.32.1.0 I experienced an extremely slow Data Lookup when entering a call sign in the input field. It takes well over 3 minutes before Name, Grid etc. gets populated and almost double that to load the right side map if lucky. Sometimes (when patient) a notification pops up saying: [WARNING SLOW RESPONSE FROM EXTERNAL SOURCE: 14559.8253].
The right side map stays green completely green (at that initial zoom level) with the red grid box and blue line drawn. When zooming in no map details are loaded. When zooming out (substantially, blurry contours of my state become sort of visual after a substantial loading delay. Pin of own QTH is drawn in as overlay correctly. Grid position box of the target seems to be plotted in the correct direction and distance. Sometimes the right side map shows "Exception: The Operation has timed out" in red text, while the map shows in blue text: "We are sorry, but we don't have imagery at this zoom level for this region".
I noticed something funny with the QRZ button on the right (globe icon), now it works as a toggle like on (green) off (dark and blue). However no matter what state, when pressing the button the QRZ page of the call sign comes up practically instantly.
In the settings the Info providers QRZ and HAMQTH respond with a green check mark. QRZ almost instantly, HAMQTH with an approximately 30 seconds delay. Disabling HAMQTH did not make a difference in the exteremly slow Data Lookup.
Page 2 of the Info Providers in the settings are set as: Use Clublog database [checked], Use CTY database [checked], Show Profile image [checked].
REALTIME Prio1: External source, Prio2 Clublog, Prio3 CTY.
HISTORIC Prio1 Clublog, Prio2 External source, Prio3 (nothing).
I Re-installed v2.32.1.0 (over the former installed v2.32.1.0) after a new download from the Log4OM website. No improvement.
I uninstalled and re-installed v.2.32.1.0 with still no improvement.
In the Settings menu under Update Resources, I performed all of them, resulting in no improvement.
While I was at it, I did all the Maintenance things in the Settings menu too. No improvement.
When typing an earlier used target call sign, the Data Lookup is much shorter. About 2 or 3 seconds. So the cache from Clublog works fine. Eventhough you still don't get a good right side map.
Left side world map looks fine by the way.
Funny detail, when you cancel with the red X button on the right during the Data Lookup, the call sign field and others get erased but Data Lookup keeps being displayed in the call sign field. After a long while you'll either get a time out notification or the data still gets displayed while the call sign box is empty.
I'm running Windows 11 Pro, version 22H2 in a VM on a quite beefy Linux machine, however a clean "bare metal" test install on a laptop resulted in the same painstaking disappointment.
Internet approx. >150/20 Mbps (down/up), Latency 29 ms.
So, as of now I'm running out of things to try and good advice is definitely appreciated.
v2.32.1.0 Extremely slow Data Lookup after entering callsign.
- G4POP
- Log4OM Alpha Team
- Posts: 10828
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Try settings\Program Config\Performance - Click the 'Performance check' button
With Win11 I get the following
Worked before on 200 calls
10ms (105424 CPU cycles)
1200000 calls/minute
Sunrise/sunset check...
4ms (44420 CPU cycles)
1500000 calls/minute
List of 200 call signs
5433ms (54331061 CPU cycles)
2208 calls/minute
Callsign statistic search...
2ms (21906 CPU cycles)
6000000 calls/minute
VOACAP test...
Performance test COMPLETE
You could also try turning of Voacap
With Win11 I get the following
Worked before on 200 calls
10ms (105424 CPU cycles)
1200000 calls/minute
Sunrise/sunset check...
4ms (44420 CPU cycles)
1500000 calls/minute
List of 200 call signs
5433ms (54331061 CPU cycles)
2208 calls/minute
Callsign statistic search...
2ms (21906 CPU cycles)
6000000 calls/minute
VOACAP test...
Performance test COMPLETE
You could also try turning of Voacap
73 Terry G4POP
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
@G4POP, Thanks for the quick reply!
My results with only "Perform call search on leave" disabled. Everything else is enabled. (unchecking the boxes in the performance tab didn't cause any substantial performance gain). Disabling VOACAP didn't make a substantial difference either.
Performance test start on 200 calls...
--------------------------------------
Worked before on 200 calls
6ms (65332 CPU cycles)
2000000 calls/minute
Sunrise/sunset check...
0ms (992 CPU cycles)
Performance test COMPLETE
Just to be clear, I didn't remove any text in the test results. However my report looks different somehow.
My results with only "Perform call search on leave" disabled. Everything else is enabled. (unchecking the boxes in the performance tab didn't cause any substantial performance gain). Disabling VOACAP didn't make a substantial difference either.
Performance test start on 200 calls...
--------------------------------------
Worked before on 200 calls
6ms (65332 CPU cycles)
2000000 calls/minute
Sunrise/sunset check...
0ms (992 CPU cycles)
Performance test COMPLETE
Just to be clear, I didn't remove any text in the test results. However my report looks different somehow.
- G4POP
- Log4OM Alpha Team
- Posts: 10828
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Did you scroll right down to bottom of the list of calls?
73 Terry G4POP
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
I just did a performance check here as well. Here is a screen shot.
- G4POP
- Log4OM Alpha Team
- Posts: 10828
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Try again with all boxes checked,,it should resemble this
73 Terry G4POP
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Tried it again with all boxes ticked and same result.
- G4POP
- Log4OM Alpha Team
- Posts: 10828
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Version Number???????????????????
Exactly when is it slow?
73 Terry G4POP
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Log4OM V2 version: 2.32.1.0
I tried the Performance test again and it doesn't give more info than posted earlier. (Screenshots below)
Also added is the report from the Self-help in the Help menu. I only X-ed out my passwords. (txt file under the picture)
Cheers, Wim - KX4UI
I tried the Performance test again and it doesn't give more info than posted earlier. (Screenshots below)
Also added is the report from the Self-help in the Help menu. I only X-ed out my passwords. (txt file under the picture)
Cheers, Wim - KX4UI
- Attachments
-
- 1_PerformanceTest.jpg (155.91 KiB) Viewed 721 times
-
- 4_SelfHelpReport.txt
- (2.29 KiB) Downloaded 49 times
Re: v2.32.1.0 Extremely slow Data Lookup after entering callsign.
Here are two screenshots with:
1- When entering a callsign. (Note the time in the Start field)
2- When the DataLookup result poped in. (Note the time again).
As good as a 3 minute delay as I lost a few making the screenshots.
Also note the right side map...
Cheers, Wim - KX4UI
1- When entering a callsign. (Note the time in the Start field)
2- When the DataLookup result poped in. (Note the time again).
As good as a 3 minute delay as I lost a few making the screenshots.
Also note the right side map...
Cheers, Wim - KX4UI