memory management

Tech Optimizer
September 1, 2026
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.
AppWizard
August 31, 2026
Google will implement new memory management policies for Android applications starting in February 2027, which will enforce specific memory limits based on device RAM. The defined limits are: - For 4GB devices: 2GB in the foreground, 1GB for user-perceived services, 1GB in the background. - For 6GB devices: 2.25GB in the foreground, 1.25GB for user-perceived services, 1.25GB in the background. - For 8GB devices: 2.25GB in the foreground, 1.5GB for user-perceived services, 1.5GB in the background. - For 12GB devices: 3.25GB in the foreground, 1.75GB for user-perceived services, 1.75GB in the background. - For 16GB devices: 4.25GB in the foreground, 2GB for user-perceived services, 2GB in the background. Devices with more than 16GB of RAM will be largely exempt from these restrictions. The changes are motivated by RAM shortages and the impact of artificial intelligence technologies on memory availability, aiming to maintain device performance and user experience. Apps exceeding these memory limits may face reduced functionality or removal from the Google Play Store.
AppWizard
August 28, 2026
Google has introduced new guidelines to improve memory management for Android applications due to a shortage of memory, requiring developers to reduce their apps' memory usage by February 2027. Smartphone manufacturers are responding to memory shortages by decreasing the memory in devices, with many entry-level smartphones now featuring only 4GB instead of the previous 6GB to 8GB. Microsoft is also optimizing Windows 11 for devices with 8GB of memory to ease the need for upgrades.
AppWizard
August 24, 2026
Google announced a trend where new mobile devices are maintaining or decreasing their physical memory capacity due to rising memory prices, referred to as "RAMageddon." With the rollout of Android 17, a new mechanism allows the operating system to manage memory more efficiently by redirecting data usage to zRAM before forcibly closing apps. This feature helps maintain device performance but may still cause delays during data decompression. Developers are encouraged to optimize their applications for these new memory constraints. Additionally, users can enhance their device security by disabling location services, Bluetooth, reviewing app permissions, limiting background data, and disabling installations from unknown sources.
AppWizard
August 22, 2026
Samsung Galaxy smartphones will benefit from the new Android 17 feature that imposes per-app memory limits, preventing any single app from monopolizing RAM. This feature is already active on Pixel devices and is expected to be adopted by other manufacturers, including Samsung, in the coming year. Android 17 allows the operating system to compress memory pages and terminate apps that exceed their memory limits, optimizing RAM usage without noticeable disruptions for users. This update aims to improve multitasking by allowing more applications to remain active in the background, particularly benefiting devices with limited RAM. Samsung's One UI already includes memory management tools, but the new system in Android 17 operates at a deeper level to enhance overall device performance. While no timeline for implementation has been announced, One UI 9 is based on Android 17, and the feature is anticipated to significantly improve user experience on Galaxy devices.
AppWizard
August 20, 2026
Google is implementing stricter memory management for Android applications, extending memory limits for individual apps introduced with Android 17 to devices with 4GB to over 16GB of RAM. The new strategy involves transferring app data into compressed memory (zRAM) when an app reaches its memory limit, which may slightly decrease performance. If an app continues to consume excessive memory, Android can terminate it. Google encourages developers to optimize their apps for these new constraints and is providing tools and resources to help identify high memory consumption issues. Users with limited RAM devices may experience fewer slowdowns, but apps that require substantial memory may face performance challenges or closure if not optimized.
AppWizard
August 20, 2026
Android 17 introduces expanded per-app memory limits to enhance performance on devices with 4GB to over 16GB of RAM. This update aims to prevent any single application from monopolizing system resources, which can cause sluggishness. If an app exceeds its memory allocation, Android can compress its data or terminate the app to maintain performance. Users will experience smoother navigation and improved performance, especially on devices with limited RAM. Developers must optimize their applications to meet the new memory constraints, or risk slowdowns or closures. Google is providing tools to help developers address memory-related issues.
Winsage
August 11, 2026
A developer has adapted Microsoft Word 1.1a, originally for 16-bit x86 systems, to run natively on modern 64-bit Windows PCs through a project called “Opus.” This adaptation compiles the original source code into a genuine x64 application, avoiding the use of emulators or virtual machines. The developer translated incompatible segments of the original code, including 16-bit assembly language, into C or C++, while mapping Win16 functions to modern Win32 APIs. The project retains original resources and copyright notices, and is hosted on GitHub without a broad open-source license. Automated testing has been implemented to ensure functionality mirrors the original application. Microsoft has previously published similar historic projects, but this port is an independent effort, providing insights into early Windows software architecture.
Winsage
August 4, 2026
Pavan Davuluri, Microsoft’s Executive Vice President for Windows and Devices, criticized LG for including non-Microsoft pop-up ads on Windows machines and discussed upcoming enhancements for Windows 11. Notably, promotional content will be removed from local search results, a change that raises questions about its classification as an improvement. Many updates to Windows 11 have focused on removing unwanted features rather than introducing new ones, particularly in applications like Notepad and Paint. Davuluri also mentioned improvements in memory efficiency and latency but did not provide a timeline for these changes. The focus on optimizing memory management is seen as a response to declining PC sales due to high RAM and SSD prices, prompting Microsoft to reassess RAM requirements for Windows 11.
Search