Log4OM

I am currently running version 2.20.0.0.
For the past several releases I have noticed that the software has become slower and slower.
It takes 5-10 seconds to get from one data entry field to the next.
Auto-filling from callsign can take several seconds and meanwhile text entry is not available.
When I checked task manager Log4OM was using something like 500MB of RAM.
I have noticed that WSJTX is losing decodes and sometimes not decoding at all but when I shutdown Log4OM, then WSJTX goes back to normal operation.
Granted, my PC is pretty wimpy (see info dump below) but I don't see any reason why logging software needs to be so resource-intensive.
So my questions are:
1. Has anyone else noticed this?
2. Seems it is time for an optimization pass of Log4OM to improve speed and memory. Is this planned?

Thanks!

73, Mike KK7ER

OS Name Microsoft Windows 11 Home
Version 10.0.22000 Build 22000
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-D6K4T2L
System Manufacturer LENOVO
System Model 81A7
System Type x64-based PC
System SKU LENOVO_MT_81A7_BU_idea_FM_FLEX 6-11IGM
Processor Intel(R) Pentium(R) Silver N5000 CPU @ 1.10GHz, 1101 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date LENOVO 6QCN50WW, 7/9/2019
SMBIOS Version 3.1
Embedded Controller Version 1.50
BIOS Mode UEFI
BaseBoard Manufacturer LENOVO
BaseBoard Product LNVNB161216
BaseBoard Version SDK0J40700WIN
Platform Role Mobile
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.22000.1"
User Name DESKTOP-D6K4T2L\Mike
Time Zone Pacific Standard Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.83 GB
Available Physical Memory 1.26 GB
Total Virtual Memory 14.3 GB
Available Virtual Memory 11.0 GB
Page File Space 10.5 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

Mike:

With all due respect, it also seems to me that clients have a similar obligation to optimize their resources and I think that a 1.1 Pentium with 4gb of RAM just doesn't cut it.

I have an eight year old desktop, too old to run Win 11, but it is an Intel I5 with 8 GB of RAM and LOG4OMV2 runs just fine in conjunction WSJT-X, JTAlert, Brave Browser and all else going on at the time.

Charlie
W4EBB

By the way, Lele is try to optimize the V2 processes all the time but if more options the users want
each more RAM & processor speed is needed. My "oldest" PC is a Dell Workstation with a Quadcore
@3.7 GHz and 8 GB Ram and 2 SSD drives. Log4OM is running well on it.

My Laptop is a 6 core @3.2 GHz and 16 GB Ram with W11 and Log4OM always runs stable and quick.

If you run old machnines only you can optimize the work of V2 in the Performances Tab in the program
configuration or in the award preferences wher you can put awards from the "Active Awards" to the
"Non active Awards" list. Other option is to minimize the contacts in the recent QSO list. In my log are
more than 27k contacts but visible are only 200. As more are in this list as more memory is used.

So play a bit with the setup to optimize all for your machine ....

@Charlie, no disrespect taken.
But don't let the brand naming fool you.
The system is a Lenovo Flex 6 11 with an Intel Gemini Lake CPU (dubbed Pentium Silver).
It is around 5 years old.

73, Mike KK7ER

@Juergen, thank you!
This very helpful.
I'll work on optimizing the settings over the weekend and report back.

73, Mike KK7ER

Hi Mike,
problem is probably related to the large memory usage made by Log4OM.
This will allow us to keep in memory TONS of data, clublog info, CTY data and much other things but that makes the application very memory hungry.
I'm working on that to bring back some info on disk, in order to free up a bit the memory usage

Some things I've done over the years to help with performance:

• Setup AV exclusions for Log4OM installation folder, database location, config directory, Omnirig path, etc.

• I've found in the past that poor performance was usually related to cluster activity. The latest versions with throttling have been a huge help. The default spot age is 60 minutes. I changed that on my install as 60 minute old spots are not useful most of the time. I don't know how much that helps, but it must relieve some memory to expire old spots more quickly.

• Setup filters at the cluster level so that Log4OM doesn't have to process things you're not interested in.

• Turn off any features you don't use. VOACAP, stuff in Performance section, etc.

Without getting into the spec's of my PC.
I have just upgraded Log40M from ver 2.19 to ver 2.20, and I think the reactive speed has increased.

I know I don't use all the features of the program, but I am more than happy with it's performance

so good on the development team

I'm glad to report that after going through all the settings and disabling everything not required for actual logging, Log4OM does not appear in the top 15 tasks in task manager (sorted by CPU utilization). It is using 668MB of memory which is a little alarming but that does not appear to be having a negative impact on system or wsjtx performance. Thanks to all who commented.

73, Mike KK7ER