![]() (51) GUI: Switch to 'KB' suffix on memory metrics to standardize (49) GUI: Try to set critical level I/O priorities despite being reserved for system paging operations. (49) GUI: Show 'Update not available' message box on same monitor as application (49) GUI: About dialog: Remove 'translated by' (49) GUI: About dialog: Add 'Help Translate Process Lasso' syslink (47) GUI: Add 'View / Graph components / Show power profile' to toggle power profile text on graph (43) GUI: Support Dark Mode for Win10 build 21286 (43) GUI: Replace active processes listview embedded CPU utilization visual with text (unicode blocks) based representation (41) Core: Fix SmartTrim log entry possible integer underflow on RAM freed display (39) GUI: Add 't' rule character for SmartTrim exclusion (27) Core: Strip unavailable CPUs from CPU affinity prior to their application to handle system config change to CPU count (19) GUI: Add new menu item 'Options / Log / Configure sampling. (19) Core: For process creation log events, remove 'UNKNOWN PARENT' text when parent doesn't or isn't applicable (now empty string) (19) Core: Add periodic process sampling function (emits to CSV) (17) Core: Tweak default log file size limit (17) Core: Add registry setting for max log file size before rotate (HKLM\Software\ProcessLasso\MaxLogFileSize) (15) GUI: Integrate more languages to Crowdin (11) GUI: Adjust default column ordering of Active Processes listview (7) Localization: Integration with Crowdin (translation platform) (5) GUI: When when adding SmartTrim exclusion by context menu use basename if no pathname available (5) GUI: Check 'Induce Performance Mode' context menu item when appropriate even if no pathname available (5) GUI: Add menu item for direct access to SmartTrim exclusions (5) Core: Enforce SmartTrim exclusions when only basename given (3) GUI: Add code to enable asynchronous listview updates (1) GUI: On config save error, show error message and offer to elevate (1) GUI: Further increase multi-threadedness of display updates CrowdIn integration for translations. ![]() ![]() Periodic process sampling (snapshots).Ordered CPU affinity and priority rules.Refactored log system with CSV as primary.By temporarily lowering the priority of the offending process, your PC can be saved from a full stall.” Changelog : Yes, it is true – believe it or not! It is this worst case scenario that Process Lasso was originally written to address. A single CPU bound thread running at Normal priority can bring an entire single-CPU system to a stall, as demonstrated by our graphical proof of concept below. “Windows has a particularly bad problem dealing with threads that decide they want to consume every bit of CPU time they can get their hands on ( CPU bound threads). Neben einer kostenpflichtigen Pro-Version sind zusätzlich eine Server-Edition sowie ältere Versionen für Windows XP und Windows 2000 verfügbar. Maybe I am just slow but I have a hard time reading them.Process Lasso ist ein automatisiertes Windows Prozessmanagement- und Optimierungs-Tool für Windows Vista, 7, 8 und 10, das die Reaktionsfähigkeit des Systems - besonders bei hohen Prozessorauslastungen - durch einen eigenen Algorithmus positiv beeinflussen soll. I feel this is very important, since it would indicate an almost certain CPU bottleneck.Ģ0862675 said:I have a couple of suggestion to improve the readability of the CPU load chart - and make it more informative: I'd like there to be a "fully loaded" group of 99 - 100% (maybe 98 - 100%, or 98.5 - 100%, depending on the precision of the data recording). The current graph doesn't show this definitely, since the high loads on the two threads may have occurred at different times in the test.Ģ) Change the value groups of the CPU load: 86% to 100% is much too wide of a gap. you could easily see how much of the time 4 or more threads were highly loaded *at the same time*. I think this display would be better than the current one, because you could see the performance profile at a glance: the colors would shift from highly loaded at the top to slightly loaded at the bottom. ■Display these as you do now - only now the top bar displays how the highest loaded CPU thread - whatever thread it happened to be at the time - was doing throughout the entire test. (The spreadsheet function LARGE is your friend here.) ■For each data point, assign the loads to graphs called "Highest loaded thread", "2nd highest", "3rd highest". ■Record loads per CPU thread for each point in time. I have a couple of suggestion to improve the readability of the CPU load chart - and make it more informative:ġ) Analyze the CPU thread loads in descending order:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |