Open PetbkA opened 1 year ago
Is an option to keep file closed (in "Advanced" tab) enabled? That could cause each read operation to reopen a file on network share and slow each operation.
Is an option to keep file closed (in "Advanced" tab) enabled? That could cause each read operation to reopen a file on network share and slow each operation.
23.07.0.1540 Qt6 x64 - yes, it had been enabled. Disabling it fixed the problem (or at least speeded up scrolling).
But won't reading the logs on shares with disabled option block writing to the log by the app which owns it? Right after disabling the option I noticed that log which had new events every ten seconds stopped showing them on reload
It confirms that reopening file every time to read new data from share is costly. Adding a delay before closing the file might solve the issue with scrolling. But initiating a new scrolling after the file was closed might still be an issue.
I have no problem disabling the option. But I'm afraid that new events won't be shown even on "manual" reload 'cause remote app can't add them 'cause log will be blocked by klogg.
UPD: just tested some logs and can confirm that everything's fine - remote app can write to log
OS: Windows 10 LTSC 2021 (version 21H2) x64 Klogg: 23.04.0.1331 Qt 5.15.2
Log opened from slow share or disk is being displayed slower than from fast local storage.
Size of the log doesn't matter - I've found the problem on 35 KByte one.
Definitely not #534, although simliar