NewApp Digest
search bot

CPU usage

Best Antivirus for Windows 2026: 5 to Install, 1 to Avoid
Tech Optimizer
September 16, 2026

Best Antivirus for Windows 2026: 5 to Install, 1 to Avoid

Windows is the only desktop platform where antivirus software is essential. Microsoft has patched many vulnerabilities, but the OS still allows installations from unverified sources and connects to potentially untrustworthy networks. As of 2026, the top antivirus solutions for Windows include: - Norton 360: Best overall, with a full scan time of 13 minutes and 22 seconds, robust firewall, and up to 250 GB cloud backup. - Bitdefender: Best for older PCs, maintaining peak CPU usage at 11% and memory at 183 MB during scans. - Avast One: Best free option for Windows 11, achieving a perfect score in AV-TEST. - NordVPN Threat Protection Pro: Best for VPN users, blocking 90% of malware. - McAfee+: Best for households with multiple devices, offering unlimited coverage but is the slowest scanner. - Microsoft Defender: Best free option included with Windows, awarded Top Product by AV-TEST. Norton 360 has a 99.8% detection rate and offers a 60-day refund window. Bitdefender also has a 99.8% detection rate with low resource usage. Avast's free version is effective, while NordVPN provides integrated malware protection for existing VPN users. McAfee is suitable for large households but has slower performance. Microsoft Defender is adequate for single users practicing safe browsing but lacks multi-device support. Kaspersky is unavailable in the U.S. due to supply chain concerns.
Improving Lakebase Postgres compute cache
Tech Optimizer
September 11, 2026

Improving Lakebase Postgres compute cache

Lakebase Postgres employs a disaggregated storage model that enhances data management through efficient caching, utilizing an object store like S3 for backups. The caching operates on two layers: within distributed storage for optimizing write and read performance, and on the Postgres compute side for ultra-fast access to frequently accessed pages. Traditional Postgres caching involves shared buffers and the OS page cache, which leads to double buffering and inefficiencies. Lakebase Postgres addresses these issues by implementing a local file cache (LFC) and larger shared buffers, allowing for more effective memory utilization without the drawbacks of the OS page cache. The shared buffers are set to a maximum of 1 GB, while the LFC can utilize up to 75% of DRAM. The introduction of huge pages reduces memory management overhead and improves performance, resulting in significant throughput increases and reduced latency in production environments. Recent enhancements have shown up to 2× throughput improvements and substantial reductions in CPU usage. The focus is now on extending these benefits to autoscaling Postgres computes, with plans to implement dynamic shared buffers and autoscaling huge pages.
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.
Windows Search still can’t find half my files, because Microsoft fixed the wrong part
Winsage
August 28, 2026

Windows Search still can’t find half my files, because Microsoft fixed the wrong part

Windows 11's native Search feature has been improved with a new indexing system that automatically indexes frequently accessed folders. The latest build, 26100.9267, allows search results to appear after two keystrokes and is more forgiving of typographical errors. Users can choose between web or store suggestions. However, issues persist, such as files remaining invisible in indexed folders. Users have two indexing options: Classic mode, which covers limited locations, and Enhanced mode, which indexes all partitions but may affect battery life and CPU usage. Many users prefer third-party alternatives like Everything, which indexes files directly from the NTFS Master File Table without requiring mode selection. Despite improvements, the overall search experience in Windows remains unsatisfactory.
Search