Log4OM

Hello FM,

My Log4om is getting very slow, in start up and in the dxcluster screen.

When I click on a call and new spots are coming in the prog takes just the call above the one I clicked on.

Anyone else this problem ?

73 - Rudi - ON7CL

Don´t have this problem with AMD Quadcore, 4 x 3600 MHz and Windows 10 Pro 64 Bit. Near 25000 contacts in the Log.
I think before anybody can try to help you we need more information about your Windows Version and the used hardware

Hi,

This is the system, and 22500 qso's in the log.

73 - Rudi - ON7CL

Hi Rudi,

should be enough "power" that your system has. The machine here is working with 8 GB Ram and 4 x 3600 MHz but i think that´s not the problem.

What i have seen is that Log4OM startup is much slower if i use my surfstick when the internet speed is low. The cluster needs a longer time to connect and so the startup sequence is longer but with good internet speed no problems here.

For your information I have test machines here ranging from very old Pentium laptops with not much ram to i5 machines with 8gb ram running Windows XP, Vista, 7, 8 & 10 using a database containing 55000 QSO's and the speed difference between all operating systems is negligible.

A slow internet connection could slow things down on start up but I would expect the 'Not Connected' warning to be displayed if a connection was not made after a very short period of time.

Perhaps you should check for a faulty or fragmented hard drive, virus, malware or some other problem outside of Log4om especially as we have many thousands of users that are apparently not experiencing this issue.

Hello FM,

All verified: internet connection, defragmentation, virus, malware.

Still the same problem.

73- Rudi

Hi Rudi, please check computer Hard Drive activity. I have worst PC (Pentium core2) Win7 but I was replace all mechanical HD for new SSD drives.
My computer has now new live Log4OM works OK.
73! Pawel SQ5LTL

Hi,

It's a new computer, with other more powerfull progs I have not any problem.

73 - Rudi - ON7CL

please check in the program log. Timings are accurately reported here.
Try to find the larger gap in the log, this is probably the source of the issue.

What database are you using? Have you tried starting log4om with a new profile (without database connected)?