Hi Everyone,

My team has reported an increase in the amount of time it takes for LogFusion to startup and become 'responsive'. This seemingly happened at the launch of 6.6. I noticed this myself and didn't think anything of it until my team mentioned it as well. Are there any steps we can take to decrease the startup times?

Thanks

I've noticed a significant delay in loading up and interacting with the ui.
In case this helps, here's my debug.

I'm afraid I can't say. I hadn't used it in a while because it always felt a bit slow. But I was working with logs again,installed it again, and it feels so much worse now, so I popped in here about it.

I started off with the stable version before moving to the beta, the issue is there as well.

I'll say that logfusion is some of the slowest software to launch that I've experienced,and I use *insanely* fast hardware.
(13900k, p5800x optane nvme (datacenter hard drive with extremely low latency, its somewhere between memory and ssd speeds)
Was trying to poke at it today to see what could be possibly done to fix it, would love some ideas. Have yet to hook it up to procmon or a debugger, but its enoguh that I'm going to start looking for an altenrate software soon if it doesnt speed up.
To note - this slow launch speed is even if it has zero logs to open at startup.

Heres a debug log, including performance metrics turned on.
Unsure why the debug log has so much info about my monitors.

FYI - DisplayFusion tends to be laggy too, I try to not leave it running and just load it when using it to restore/set monitor profiles.

This is with th last stable verison 6.6, I can try the 6.7 beta if you think it would help.

Looks like I already tried running procmon to diagnose the issue last time it annoyed me, for the 6.7.4 beta. - https://www.logfusion.ca/Discussions/View/logfusion-67-beta-4-now-available/?ID=be1bf859-6b4d-4de9-a514-fd94c6b302ea#2

Just ran it through procmon again and peered through the debug logs - theres a ton of font scaling related info, but disabling that diddnt change performance noticiablly.

Tried the latest beta too, same issues. Heres a perfmon log.

I was using LogFusion v4.1 on Windows 7 and everything worked perfectly.
However, after upgrading to Windows 11, the startup became very slow, even when nothing else was open.

So, I tried downloading versions 5.0, 6.6, and 6.9.1-Beta3, but there was no improvement.

It takes more than 7~13 seconds to see an empty interface.

I tried using dotTrace to analyze the startup time and came to some conclusions,
but I couldn't understand most of them.

I hope the official team can try to reproduce the issue to see if it can be resolved.

The snapshots and flame graphs have been uploaded to the attachment.

My operating system is
Windows 11 IoT Enterprise LTSC Edition,
version 24H2,
installed on 2024/11/6, All Is Empty.
with the OS version 26100.2161.
The Windows Feature Experience Pack version is 1000.26100.32.0.

yeah it's dog slow even on very very fast hardware. i switched to using klogg instead.

maybe try lazy loading the event log stuff, I do know Windows event log handling can be quite slow.

but Even after loading it's still lags. seriously try klogg and log fusion at the same time.

in some ways I'd rather use log fusion as it's more featured but the speed difference is a game changer.