Looking for advice for a not so fast PC

[VA2SS]

Hi,

I am a new user of Log4OM. I'm now using Log4OM 2.0 and really enjoy it so far. I can see there is « a lot » of work behind this software... congratulation to the development Team. I'm using Log4OM+OmniRIG with WSJT-X and FLDigi with success so far. LoTW integration works flawlessly too.

My only concern is the following. I'm running Log4OM on Panasonic Toughbook CF19 Intel i5 Core2 Duo with 8Gb RAM using SSD using Windows 10 Pro. My former programmer skills tells me that it seems there is a lot of processing behind the scene that is done in the background, and the execution is somekind not so fast.... let's say laggy.

My question is the following : Which options I should try to disable to lower the need for processing? I tried several options by reading the manual, but no lock so far. Any advice that could help me?

I was using other logbooks before that were a lot more responsive.

Thanks for helping me.

Best 73.

[G4POP]

Firstly I am surprised that you have a problem with that spec of PC because thats exactly what I was using until recently without issue, I only changed to my current i7 crate when the i5 mother board went belly up!

However make sure your using the very latest release of Log4OM version 2.11.0.0 and if its still 'Laggy' then in Program config/Performance tab disable the three check boxes and see if that improves things.

[VA2SS]

Hi Terry,

I unckecked the 3 check boxes... already tried. I can see not much improvment. I did a performance test, there is the results if this can help.

Performance test start on 10 calls...
Worked before...
38ms (386603 CPU cycles)
Sunrise/sunset check...
1ms (19075 CPU cycles)
CQ Zone identification from Clublog database check...
13ms (139036 CPU cycles)
CTY Data checks...
3ms (38544 CPU cycles)
Callsign statistic search...
2ms (22390 CPU cycles)
VOACAP test...
Calculated voacap data for FN21wa Max 0
Calculated voacap data for IN82eo Max 0
Calculated voacap data for KH02mt Max 0
Calculated voacap data for GF17sb Max 0
Calculated voacap data for FJ49gj Max 0
Calculated voacap data for CO46xp Max 0
Calculated voacap data for CO46xp Max 0
Calculated voacap data for QO94jg Max 0
Calculated voacap data for ON26kl Max 0
Calculated voacap data for LP74jq Max 0
855ms (8552446 CPU cycles)
External service search...
IW3HMH Daniele Pistollato
G4POP Terry Genes
LA9FFA Rolf Flaathe
NN7D Douglas R Munday
VA3AG Aldo Galati
KI5IO Nolan E Kienitz
DF5WW
OE6CLD Ing. Claus Stehlik
KD0ZV Rich R Mc Cabe
IQ3ME Associazione Radioamatori Italiani Sezione Di Mestre
1390ms (13908964 CPU cycles)
OVERALL Country statistic recalculation...
1354ms (13548443 CPU cycles)
OVERALL Gridsquare statistic recalculation...
1759ms (17591877 CPU cycles)
OVERALL Worked before statistic recalculation...
1ms (15393 CPU cycles)
Performance test COMPLETE

[G4POP]

Try turning off Voacap

How many qso's in your log?

[VA2SS]

VOA disabled... done.

I have 7200 QSO's.

I think I might found something. When I recently reinstalled from scratch, Windows installed generic drivers for almost every interface. I will try to update some drivers, like storage, etc...

[G4POP]

Well it's not the number of qso's slowing it, I have test logs with 80K qso's

Could be drivers, windows changes many things including security settings so check everywhere

[VA2SS]

.....Found nothing... everything seems normal.. at least with all my other apps. So it should be a normal behavior with Log4OM and my PC I means.. it is what it is.... I probably asking too much... it is a little bit faster on my Surface Book 2 i5.. but not much.. still lag when starting the app and everything is loading up... I mean even when starting the app... it loads slowly then things appears slowly until everything has been processed....... Thanks anyway. I still like the app very much. I will upgrade my PC one day.

Best 73

[VA2SS]

Hi, I found the culprit..... a generic storage driver... I finally found the right one made for my laptop.... now optimized with faster process speed.

Everything is now under control. I was very sad, because I really like Log4OM 2. I searched over a long period to find a modern and effective logbook software. Hi!

Best 73 and thanks fror your support.

Jeff VA2SS

Well it's not the number of qso's slowing it, I have test logs with 80K qso's

Could be drivers, windows changes many things including security settings so check everywhere

[G4POP]

I am pleased that you found the problem and hope that you continue to use Log4OM