Thanks for reporting this issue.

What kind of machine are you using to run LogViewPlus?  Does it have enough memory for the number of log files being accessed?  If a log file has been rolled, the Windows reported file size may not accurately reflect the size of the log entries in memory.

We performance test LogViewPlus regularly.  I will be sure to do extra performance testing before the next release to see where we can improve.  Are these performance problems application wide, or is there a specific area where you would like us to focus our testing?

The XML display issues are likely due to syntax highlighting.  You can disable syntax highlighting to improve performance.

You can find out more about the LogViewPlus Performance Profile in our documentation.

Thanks again,

Toby

I suspect it may have to do with the size of individual log entries. Some contain XML payloads as large as 3MB. When one of these is displayed, even selecting text is noticeably slow.

I used to find the performance of LVP to be fine, but now it is unusable. It takes from 30s to several minutes to display a 145KB log entry, and uses 25-30% CPU during this time. This is with a single 500MB file open and no searches or highlights. Searching in the file also takes more than 30s.

I am using version 3.0.16.