Coreprio User Interface

Coreprio v0.0.5.0 – Inclusion/Exclusion Patterns

Coreprio has been updated to allow for inclusion and exclusion patterns to be specified. These apply to all features of Coreprio. Wildcards are allowed. The console mode utility allows these as well, via the new ‘–inclusions’ and ‘–exclusions’ parameters. The full revision history is below. Add inclusion and exclusion pattern matching by process basename, -l,–inclusions […]

Read more
Process Lasso's new CPU Group Display

Lasso: Processor Group Display

Process Lasso now displays the processor group(s) an application’s threads are running on. We wrote about processor groups a while back. They exist to allow for systems with more than 64 logical CPU cores. In Process Lasso, we refer to Processor Groups as ‘CPU Groups’. By default, an application’s threads are assigned to only a […]

Read more
Coreprio User Interface

Coreprio: Bitsum’s Own Dynamic Local Mode

Coreprio is Bitsum’s custom implementation of AMD’s¬†Dynamic Local Mode. It is more configurable than AMD’s implementation, allowing the user to set the prioritized affinity, thread count and refresh rate. History When the high core count ThreadRipper 2990wx and 2970wx were developed, AMD had to make due with the 4 memory channels available in the TR4 […]

Read more
ProBalance in CPUBalance with Frequency of Action Metric for ProBalance

CPUBalance Updated to v1.0.0.68

This build of CPUBalance¬†fixes a couple flaws in the last build’s updater. I had added a safety, just in case I neglected to clear edge-node caches (ahem), but took it a bit overboard, causing a 25 second delay when a user-initiated update check was performed. This should fix that up. In other news, I found […]

Read more
Process Lasso Profiles Sscreenshot

Process Lasso v9.0.0.318 Released

This build is something of a relief to me, as it fixes all major or semi-major bugs I’ve tracked post-v9 release. Inevitably, software companies find bugs after release. That’s why we all do updates, from Microsoft to Bitsum. It is just some law of the universe. We had 6000 beta testers and 2 QA guys […]

Read more