Process Lasso v10
Process Lasso v10 has made its debut! This version refactors the log, adds a new sampling capability, allows CPU affinity and priority rules to be ordered, shortens menu captions, integrates with Crowdin, and has myriad other improvements. Let’s go through some of the many changes…
Ordered CPU Affinity and Priority Rules
We’ve had many requests from users who wanted to create ordered rulesets. That is, they want to create wildcard (or RegExp) rules that apply to many processes, but have previous rules take precedence. For instance, a user might want all processes matching n*.exe to have a CPU affinity of 0-1, but have notepad.exe be an exception with a CPU affinity of 2-3. This previously required some fancy RegExp gymnastics, but now it is simple. Create a rule for notepad.exe, then follow it with the n*.exe wildcard rule.
The log in prior versions was a binary format, thus a more accessible CSV rendition required using an export function, or the in-tandem CSV log emission option. No more! The primary log is now CSV format, so no transforms need to be done. An added benefit is reduced disk I/O since the prior format used fixed-size records. Further, all CSV operations, such as copy-to-clipboard from listviews and the new sampling feature, are run through the same code, improving consistency and interoperability. We believe the logs will now be much more usable.
A new process sampling capability was added. This will emit a periodic CSV dump of various process metrics. This is useful to audit process activity. Sure, this could easily be scripted, but we got a request to add this because many customers found that PowerShell was too heavy to run effectively during high loads. We did, however, match field names to those PowerShell would emit, where possible (some fields we report don’t exist in PowerShell’s process object).
Some of our menu captions were sentences. This didn’t present well. We’ve improved them to be shorter, and standardized them so each noun is capitalized. Some ancillary work does remain, so we’ll be continuing to enforce this new standard in future versions. As with any string change, there was hesitancy because it means all our translations must be updated. However, this needed done!
Finally, we’ve integrated with an online service called Crowdin. This took some work, and a new monthly expense, but is well worth it. Our translations are now easily edited online and collaboration with contributors is much easier. If you’d like to contribute, see this page.
For a full list of changes, see this page.
It is our hope that you enjoy this new version! Please let us know if you have any feedback.