GUI is very often in an unresponsive state


Author
Message
dennisl68-castra
dennisl68-castra
I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)
Group: Forum Members
Posts: 22, Visits: 20
I'm trying to work with high volume logs using `Merged Logs` (as I need to combine logs from different sources into one) that reaches 10 000 entries per minute. LogViewPlus is very often stuck in `Unresponsive` state or is very slow the respond to mouse actions.

I've got 7 GB of free RAM on a 12 GB system according to Task Manager.
The process LogViewPlus.exe is consuming ~3 GB of private working Memory and 50% CPU load on Xeon Platinum 8160
@2.10 GHz.


Replies
dennisl68-castra
dennisl68-castra
I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)I'm into this (245 reputation)
Group: Forum Members
Posts: 22, Visits: 20
Well, isn't that because the log files collected into RAM is getting to large?
LogViewPlus Support
LogViewPlus Support
Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)Supreme Being (12K reputation)
Group: Moderators
Posts: 1.3K, Visits: 4.4K
Yes - that seems to be the case.  LogViewPlus is resource starved because you are asking it to do a lot of work.  If you are happy with that as the explanation, then I think we can close this ticket.  However, if my understanding of the issue is incorrect, we should keep investigating.

If you see my original reply, LogViewPlus is a memory intensive program.  If you are saying a 50 MB log file takes 7 GB in memory, that sounds like a problem that I have not yet been able to recreate.  From this discussion, it seems more likely you are tailing the log files, so the number of log entries in memory far exceeds the 50 MB in the log file.

If 46 log files is 1.5 GB on the file system, this would probably be 3 GB as UTF-16.  We need to double this because LogViewPlus stores a parsed and unparsed version of the message, so 6 GB.  You are reporting 7 GB, so that seems like expected behaviour.

Also, if LogViewPlus is consuming 7 GB and you refresh the file, Windows will not necessarily free the 7 GB.  From Windows perspective, you may have plenty of memory and freeing the 7 GB will consume CPU resources.  So it may not bother until it is necessary.

The CPU usage is harder to explain, but if you are tailing 10,000 log entries per minute, between what your application is doing to create the log entries and what LogViewPlus is doing to read / process them, that might do it.

Hope that helps clarify,

Toby
Edited 2 Years Ago by LogViewPlus Support
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Login

Explore
Messages
Mentions
Search