Log4OM

Hi,

I installed v1.23 yesterday and have been using it yesterday, overnight and into today (through a horribly unpleasasnt Stew Perry warm-up event - propagation was truly awful, even for a "topband head"). Unfortunately, a potential issue that I've been conscious was (potentially) bubbling up with recent versions has now reared its ugly head beyond doubt; I'm seeing "noticeable" latency issues with this version of Log4OM; a number of basic functions e.g. entering details of a QSO, cluster related updates etc. are now causing "hangs". These are manifesting themselves as lags in user interface interactions. I had a suspicion something was afoot with previous versions when I noticed that Log4OM Communicator (this is where my instincts suggest the issue may lie) appeared to cause time delays with UI activitiy. I suspect network hangs (a strong term as they haven't been that decisive but noticeable to a jaded programmer like myself who has had his fingers burnt once too often); with v1.23 these lags appear to have passed a threshold and have begun interfering with basic operations. It could have something to do with CAT but I don't think so as I've not change anything else in my (and I concede this point) somewhat complex setup...

The PC here is no rocket ship but it's not a slouch either; a 2.8GHz dual Pentium core machine with 4gB of ram (32bit OS). It's a good box and has run quite reliably for oodles of CPU cycles but is now getting upset when I leave Log4OM running for any period.

I don't think the issue here is CPU load but rather one of network latency...

Cormac,
So far nobody has reported any latency issues and that is surprising considering there were in excess of 36000 (Thirty six thousand) downloads of Version 1.22 and so far a couple of thousand downloads of Version 1.23

This would make me believe that the issue is local to your set up, although I agree the computer spec should be more than adequate for the task.

However if you could provide a full and detailed description of what you describe as a "somewhat complex setup" perhaps I will be able to offer some advice.

One thing I found some time ago was that Google Chrome was very over active even when the browser was not running to the degree that my computer almost ground to a halt, I removed Chrome and all immediately reverted to normal, another friend of mine had the same issues with Chrome so perhaps if you are using that software you could try removing it?

Terry,

V sorry for delayed reply, pesky work thing getting in the way of radio again. I'm still having issues and am trying to narrow down/figure out what's happening. There's something not right here; I'm happy at this stage it's not CAT (suspending CAT in Log4OM has no material impact on the lags I'm seeing and CAT into my other applications e.g. FAROS propagation monitoring is without issues). All the indications are something network but that's all I can say at this point; this weekend I'm going to dig deeper and see if I can get to the bottom of it. Will report further...

Thanks for the Chrome tip btw; as it happens I'd noticed Chrome's hyper-activeness myself (it's become a right little hog hasn't it) and have been unmerciful in killing off every Chrome process I can find when I'm not using a browser. As you indicate, it certainly makes a difference.

Back with more before Monday.

Terry,

Still digging here but it's beginning to look like the culprit is something going on between SAMBA and AVAST anti-virus that's screwing up networking in general including Log4OM communicator. With grovelling apologies to Log4OM for jumping the gun. How could I have doubted - )

Doubts are the first cause of bug fixing
Thanks for reporting!