Kbs

I ran my own experiments to better understand how Hyper-Threading works internally on Windows, using hand-written assembly benchmarks — from single-register multiplications to SHA-256 hashing.

I just encountered an interesting exception in LabVIEW when the Median Filter was called for a float image containing a NaN value. It works as expected for small images, but I found one that caused a crash.

If you have a dual-socket CPU, each socket may have dedicated RAM assigned to it. This can lead to performance penalties when a processor accesses memory from the “wrong” memory bank. Below is a simple benchmark and an explanation of how to utilize the full bandwidth properly.

Installation of gcc and clang is not very complicated, but there are some issues in corporate environment which I would like to note.

A practical example of compiler optimization side effects: when the volatile keyword becomes essential

To get DeepSeek running on your PC you will need enough RAM, and it is quite easy with llama.cpp. Below step by step guide and results.

Sometimes we need to check MD5 or SHA256 checksums for downloaded files. An easiest way:

certutil -hashfile <FILE> MD5

or with PowerShell:

Get-FileHash <FILE> -Algorithm SHA256

In attempt to install winget on Windowss 11 LTSC as recommended by Microsoft I’ve got error message. Below the simple workaround

Recently upgraded CPU in my ancient laptop from i7-4800MQ to i7-4940MX, which is Extreme Edition, and need legacy Intel Extreme Tuning Utility, version XTUSetup 6.5.1.360 is compatible.

It is necessary to set Working Directory, otherwise ConEmu will not start Far Manager.

The AutoHotkey script for Win+F:

#Requires AutoHotkey v2.0

#f::
{
    SetWorkingDir("C:\Program Files\ConEmu")
    Run ("C:\Program Files\ConEmu\ConEmu64.exe")
}

Today I noticed that my computer was slower than usual. A brief investigation revealed that PowerLauncher.exe was causing other running MSI installers to fail when setting up shortcuts.

Time to time I need “quick and dirty” benchmark to check performance. Sometimes using CPU Bench from CPU-Z or AIDA, but there is quicker way with Power Shell…

I was experiencing extremely poor performance of the VMWare Workstation on a Xeon PC running Windows 11 LTSC 24H2. Below the command with some magic.

Small but useful snippet about CPU’s Name and to get it programmatically using WMI. Useful for Information and benchmarking purposes.

In some cases we need to have dedicated Drive in absence of the physical Drive. In this case we can add drive mapped to the Folder. Typically this could be done using SUBST command, but there is more convenient way.