NewApp Digest
search bot

kernel

Autoscaling Lakebase Postgres
Tech Optimizer
September 1, 2026

Autoscaling Lakebase Postgres

Choosing a database instance size without prior knowledge of the workload can lead to inefficiencies and excessive compute usage. Lakebase Postgres addresses this with an autoscaling feature that eliminates manual sizing, utilizing in-place VM resizing and a monitoring algorithm for CPU, memory, and working set size. Lakebase Postgres separates compute and storage layers, allowing independent resizing of compute nodes without affecting the database. The autoscaling algorithm relies on three signals: CPU load (cpuGoalCU), memory use (memGoalCU), and compute-cache working set size (lfcGoalCU). The CPU load is monitored every five seconds, aiming to maintain it at or below 90% capacity. Memory usage is tracked at two frequencies: overall memory every five seconds and Postgres-specific memory every 100 milliseconds, with a goal to keep usage below 75% of allocated RAM. The compute cache evaluates active data access efficiency, adjusting size based on workload. The working set is estimated using a modified HyperLogLog algorithm that records timestamps for page accesses, allowing for distinct page estimates over various time frames. The algorithm projects future working-set growth to allocate sufficient cache while capping it at 75% of RAM. Resizing the compute involves four components: the autoscaler-agent, vm-monitor, Kubernetes scheduler, and NeonVM. Scaling up occurs when any of the three goals indicate a need for more resources, while scaling down includes verification to ensure sufficient memory remains for operations. Timely adjustments in both directions are prioritized to minimize costs.
silver Android smartphone
Winsage
August 31, 2026

3 tasks that are still easier on Linux than Windows

Linux users benefit from a streamlined software update process through package managers like APT, DNF, and Pacman, allowing all applications to be updated with a single command. In contrast, Windows requires multiple update mechanisms for the operating system and third-party software, often necessitating manual checks. Most drivers in Linux are built into the kernel, enabling automatic recognition and configuration of new hardware, while Windows typically requires users to download drivers from manufacturers' websites. Linux provides clearer system logs for troubleshooting, making it easier to diagnose issues, whereas Windows error messages can be vague and less informative. Overall, Linux offers advantages in software updates, driver management, and troubleshooting compared to Windows.
Your GPU's scheduling toggle was pointless in 2020, and a growing list of Windows features now need it
Winsage
August 30, 2026

Your GPU’s scheduling toggle was pointless in 2020, and a growing list of Windows features now need it

For over a decade, Windows managed graphics card operations through a single CPU thread. In May 2020, Microsoft introduced Hardware-Accelerated GPU Scheduling (HAGS), allowing users to transfer scheduling tasks to the GPU. HAGS shifts scheduling from the CPU to a dedicated processor on the GPU, reducing CPU overhead. The introduction of WDDM 3.0 with Windows 11 21H2 requires HAGS for the basic hardware flip queue, which reduces power consumption. The advanced hardware flip queue, which addresses presentation latency, also requires HAGS. With Windows 11 24H2 and WDDM 3.2, native GPU fences were introduced, allowing the GPU to manage dependencies without CPU intervention. Nvidia's frame generation features require HAGS, while Intel's Arc B-series cards do not. The state of HAGS is determined by GPU drivers, and applications like OBS have shown caution towards HAGS due to historical issues.
Windows 11 26H2 Goes Into Release Preview Channel
Winsage
August 27, 2026

Windows 11 26H2 Goes Into Release Preview Channel

Microsoft has released Windows 11 version 26H2, build number 26300.9278, in the Release Preview Channel for Windows Insiders. This update focuses on extending the support cycle for users transitioning to 26H2. Microsoft has been rolling out support and updates since late 2024, activating essential features with each new release cycle. Enablement packages (eKBs) are crucial for the update mechanism, allowing users on versions 24H2 or 25H2 to upgrade to 26H2 with a simple eKB, while users on older branches like 22H2 and 23H2 will undergo a full feature update. Additionally, the KB5120996 update has been released for Windows 11 26H1, specifically for Windows-on-Arm devices, aligning with enhancements in the KB5120998 update for the 24H2 and 25H2 branches, which include taskbar and Start Menu customization and overall performance improvements.
Windows NT 4.0 was released on this day 30 years ago
Winsage
August 26, 2026

Windows NT 4.0 was released on this day 30 years ago

On August 24, 2001, Microsoft launched Windows XP to manufacturing. Five years earlier, on August 24, 1996, Windows NT 4.0 was released to the public, following the launch of Windows 95 in 1995. Windows NT 4.0 featured a user interface similar to Windows 95, incorporating elements like the Start button, taskbar, and Windows Explorer, while maintaining the security and networking advantages of the NT line. It emphasized business networking, with its Server edition including Internet Information Server and support for PPTP for virtual private networks. However, it faced challenges such as increased risk of system crashes due to architectural changes and limited driver availability, lacking official USB support. The legacy of the NT line continues in modern Windows operating systems, including Windows 2000, XP, and Windows 11.
Microsoft Now Says Your RGB Lighting Is Why Windows Keeps Crashing Your Games, and There Is a Registry Fix
Winsage
August 26, 2026

Microsoft Now Says Your RGB Lighting Is Why Windows Keeps Crashing Your Games, and There Is a Registry Fix

Microsoft has identified RGB peripherals and components as the source of game crashes following the August 11 Patch Tuesday rollup for Windows 11. The issue stems from drivers or code components resembling inpoutx64, which are triggered when certain games are launched. Embark Studios linked the problem to update KB5121003, and Microsoft confirmed the connection to inpoutx64.sys, although the root cause involves changes to the Windows kernel driver. A temporary workaround involves editing the registry to disable the inpoutx64 driver, though this may affect RGB functionality. Affected games include ARC Raiders, MARVEL Tokon: Fighting Souls, and The Finals on Windows 11 versions 24H2 and 25H2, with symptoms like game freezing and unexpected closures. Rolling back the update is not recommended due to security vulnerabilities it addressed. The inpoutx64.sys driver has been included with various RGB and monitoring software, and Microsoft is investigating the issue further, asking users for feedback. No timeline for a permanent fix has been provided.
Windows 11 KB5121003: Game crashes caused by inpoutx64
Winsage
August 25, 2026

Windows 11 KB5121003: Game crashes caused by inpoutx64

Microsoft has acknowledged issues with the August security update KB5121003 for Windows 11, affecting versions 24H2 and 25H2. Users reported problems such as game freezing, unexpected closures, and system restarts after installing the update. The issues are linked to drivers and software for specific RGB-enabled peripherals or components, particularly involving the inpoutx64.sys driver. Games mentioned include ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS. Embark Studios has released a support guide suggesting users stop and remove the inpoutx64.sys service as a temporary workaround. Microsoft is investigating the issue but has not provided a definitive fix or patch timeline.
Search