GUI is VERY VERY Slow
GUI is VERY VERY Slow
Something new has arisen. My GUI screen takes way too long to update. I'm running 2.28.0.0. I can click on a callsign to make a QSO. The data lookup on the GUI screen hangs usually past the end of the QSO. (I'm on FT8). I'm now in the habit of clicking on the globe to open QRZ.com which appears quickly. The QSO data is all there complete when I log it. ....and the GUI is still searching for the info to load on the main screen. I've seen comments about slow processing and have disabled VOCAP. Anything else you can suggest? The program must have the info since it populates the QSO data, but for some reason it gets stalled on posting it on the GUI window. Have 28,000 QSO's. Running my email on the side with CCUser, JTAlert, and WSJT-X. The computer seems to be handling it cuz the QRZ info pops up normally upon request. Just wondering why the GUI screen takes so long to populate. Thanks, 73, Herb, WB8ASI
Re: GUI is VERY VERY Slow
Hi,
I keep having Log4OM with slowness issues as well as freezing issues.
No matter what I tried.
VOACAP is off and I also tried to remove everything which could be processor intensive.
I love Log4OM but I am now looking for another logbook.
What I did:
- VOACAP disabled (this is what helped the most)
- Program Settings / Performances: Disabled everything
- External services disabled all live upload (Clublog, QRZ, HRDLog)
- Cluster checked Show cluster grouped
- Info providers / Configuration: Disabled use Clublog database / CTY database.
- Disabled info providers (no more qrz.com data fetching) / downloading pictures is disabled also.
After some time like after logging 100 QSO in one hour it starts being extremely slow and is unusable.
Also launching Log4OM takes a lot of time for me, it stays stuck 2 minutes on Clubloc async
Good luck
I keep having Log4OM with slowness issues as well as freezing issues.
No matter what I tried.
VOACAP is off and I also tried to remove everything which could be processor intensive.
I love Log4OM but I am now looking for another logbook.
What I did:
- VOACAP disabled (this is what helped the most)
- Program Settings / Performances: Disabled everything
- External services disabled all live upload (Clublog, QRZ, HRDLog)
- Cluster checked Show cluster grouped
- Info providers / Configuration: Disabled use Clublog database / CTY database.
- Disabled info providers (no more qrz.com data fetching) / downloading pictures is disabled also.
After some time like after logging 100 QSO in one hour it starts being extremely slow and is unusable.
Also launching Log4OM takes a lot of time for me, it stays stuck 2 minutes on Clubloc async
Good luck
73 de F4BPO Greg