You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When entopping a system with 300k processes, it takes quite a while to refresh the process list (up to a minute). Would be cool if entop could use a different update strategy when it discovers that the number of processes is huge.
For example: refresh only top 1000 processes after getting the initial list (starting with the visible ones, and then it can figure out if a process on the top list has been replaced by keeping track of the Min and Max value for the current sort column), and only get the complete process list in the background, every let's say 30 seconds.
The text was updated successfully, but these errors were encountered:
When entopping a system with 300k processes, it takes quite a while to refresh the process list (up to a minute). Would be cool if entop could use a different update strategy when it discovers that the number of processes is huge.
For example: refresh only top 1000 processes after getting the initial list (starting with the visible ones, and then it can figure out if a process on the top list has been replaced by keeping track of the Min and Max value for the current sort column), and only get the complete process list in the background, every let's say 30 seconds.
The text was updated successfully, but these errors were encountered: