Hi,
when I click on a very long log entry I get the message:
"Only the first 50 kb of this message is displayed. You can Override or Open in Editor to view the full message."
Is there a way to reduce the amount of kb that is initially loaded?

Thanks,
Markus

Hi Braun,

Currently, this threshold is not configurable. 

The purpose of this feature is to improve performance by only pretty printing large log entries when necessary.  To do this, we needed to determine a threashold for 'large'.  In our testing, we determined that LogViewPlus can pretty print 50 KB of text with minimal performance impact.  Some users had log entries which were 10s of megabytes and at that point they were experiencing performance issues with pretty printing.  This was made worse because sometimes they only accidently selected a log entry, but still had to wait for the load time.  

Hope that helps,

Toby

Hi Toby, thanks for the info!
That's seems to be exactly my issue. :-)
I have a log entry that is 214KB and takes about 70 seconds to load it into the bottom pane when I select it in the top pane.
The ovveride to load the entire entry takes about another 70 seconds.

Ah, I just found the issue. I had pretty print set to 'Numbers & Symbols'. I switched it to 'unformatted' and now the log entry loads immediately.

Awesome, thanks!

Thanks for the update Braun - glad you were able to find a work around.

140 seconds to pretty print 220KB sounds extremely slow.  I'd be happy to take a look at that if you were able to provide a sample log entry.  You can contact us via email if you would prefer to share offline.

Thanks,

Toby

Great. Here is the log entry.

With automatic syntax highlighting disabled and/or pretty print set to 'unformatted' it loads pretty quickly.
I guess that pretty print is quite slow because the log entry contains some binary data which are all highlighted as numbers?

Thanks for the sample log entry Braun, I was able to recreate the issue.

I can see where the problem is and, unfortunately, there is nothing we can do to improve the performance.  The issue here is actually with a third-party control.

What I have done instead is added a threshold based on rendering complexity - above which we can expect to have performance problems.  In future releases, syntax highlighting will be automatically disabled for complex log entries like this.

Hope that helps,

Toby

Great, thanks!