memory limits Archives

Winsage

September 13, 2026

Microsoft reveals why 32-bit Windows was limited to 4GB RAM, and it wasn’t a technical limit

32-bit Windows is commonly thought to be limited to 4GB of RAM due to its 32-bit address space, but this overlooks the role of Physical Address Extension (PAE), which allows access to more than 4GB of RAM on compatible processors. PAE enables 32-bit x86 processors to use 36-bit physical addresses. Windows allocates a 4GB virtual address space to each 32-bit application, with 2GB reserved for the application and 2GB for system use. Windows Server 2003 SP1 Enterprise can support up to 64GB of RAM, while the Datacenter edition can handle 128GB. Microsoft did not extend this capability to consumer editions due to the complexities and potential issues with hardware drivers, which often assume a 32-bit framework. Modifying drivers for PAE can be challenging, as incorrect assumptions about physical and virtual addresses can lead to memory corruption. To mitigate risks, Microsoft capped physical address space at 4GB in Windows XP SP2 and Windows Server 2003 SP1 Standard Edition. Server environments typically have more controlled hardware selections, allowing for the use of drivers that are tested for compatibility with addresses exceeding 4GB. Microsoft began discouraging the production of 32-bit systems in 2020 and ended 32-bit edition production with Windows 11.

AppWizard

September 6, 2026

Google orders Android apps to cut RAM use amid memory crunch

Google has introduced new performance standards for applications on Google Play to improve user experience and device efficiency by reducing memory consumption. Key areas of focus include dynamic memory management, efficient bitmap data utilization, and DEX code optimization. These standards aim to prevent system slowdowns and forced app closures due to insufficient memory. Google will provide tools within the Play Console for developers to monitor memory issues and access analytics through Android Vitals. The new performance thresholds will take effect in February 2027, with non-compliant applications facing publication restrictions. Additionally, all applications with login systems must support a zero-tap sign-in feature for enhanced user convenience and security.

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.

AppWizard

August 31, 2026

Google enforcing new Android app memory limits in February

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 31, 2026

The AI memory crunch has reached the apps on your phone

Google will implement new memory usage regulations for Android applications starting in February 2027, due to a global RAM shortage. Apps exceeding the set memory limits may be throttled, terminated, or face reduced visibility on the Play Store. The memory thresholds vary based on device specifications, with specific limits for foreground, background, and bitmap memory usage. Non-compliance will result in penalties affecting app distribution and visibility. The memory crisis is attributed to increased demand from the AI data center industry, leading to rising RAM costs. The new limits will first apply to Pixel devices with Android 17, and other manufacturers are expected to follow. Additionally, by April 2027, all apps on the Play Store must support zero-tap credential restoration for users transitioning to new devices.

AppWizard

August 29, 2026

Android’s new RAM rules come with a Play Store threat attached

Google will implement new regulations in February 2027 that impose per-app memory ceilings on the Play Store, requiring Android developers to optimize their apps for RAM usage. Apps exceeding these memory thresholds may be removed from the Play Store, leading to increased competition and enhanced user experience due to faster load times and improved performance.

AppWizard

August 28, 2026

Google warns Android app developers to reduce memory usage, with new thresholds set to begin in February 2027.

Google Play is implementing two key requirements to improve app quality and user experience. 1. Reducing App Memory Usage: Google Play is setting broader memory limits to prevent excessive memory consumption by apps. Developers must adhere to specific performance thresholds, including: - Dynamic Memory Usage: Monitoring memory used for an app's private data storage. - Bitmap Memory Usage: Ensuring bitmaps are not retained longer than necessary. - Optimized DEX Code: Achieving a minimum of 25% coverage with optimization tools like R8. To assist developers, Google Play has introduced tools for monitoring memory usage and tracking crashes due to insufficient memory. Warnings will be issued if apps exceed the new thresholds. 2. Ensuring a Seamless Device Migration Experience: Starting in April 2027, all apps supporting user sign-in must use the Android Restore Credentials API for automatic restoration of sign-in states when switching devices. Game apps are currently exempt, but guidance will be provided for handling authentication in gaming applications in 2027.

AppWizard

August 27, 2026

Google tells Android app developers to cool it on memory use, or else

Google has announced new memory-usage restrictions for Android applications to address the ongoing RAM crisis. These restrictions require developers to comply with new memory constraints to ensure smoother operation across devices. The initiative coincides with the rollout of Android 17, which is being introduced on devices like the Pixel 11 Pro and 11 Pro XL, both of which have less RAM than previous models. Developers must consider varying RAM configurations, ranging from 4GB to over 16GB. Applications that exceed the memory limits may experience reduced performance, slowdowns, or termination, and may face diminished visibility on the Google Play Store. These memory limits will take effect in February 2027, providing developers time to adjust their applications.

AppWizard

August 27, 2026

Google forces Android apps to use memory more wisely as RAMpocalypse rages

Starting in early 2027, Android apps on Google Play must meet new memory performance standards due to rising RAM prices and consumer demand for streamlined smartphones. Google is concerned about a potential "ecosystem-wide memory crisis" and aims to improve memory efficiency in app development. The new standards will be implemented in two phases: the first phase in February 2027 will set thresholds for undesirable behavior and code optimization, while the second phase in April 2027 will enhance device migration with a zero-tap credential restoration feature. Specific memory limits include: - For devices with 8 GB of RAM: foreground app usage capped at 2.25 GB, 1.5 GB for user-perceived services, and 1.5 GB for background processes. - Devices with more than 16 GB of RAM will be largely exempt from these restrictions. - Bitmap memory usage limited to 200 MB for user-perceived and background services, with a cached limit of 400 MB across all devices. - Gaming applications will have different memory requirements. The DEX code optimization mandate aims to improve memory utilization, app launch speed, and runtime performance. The zero-tap sign-in requirement in the second phase seeks to streamline device migration and enhance security, addressing risks associated with manual sign-ins.

AppWizard

August 27, 2026

Google to tighten oversight of Android apps’ memory use

Google is implementing stricter oversight on RAM usage by applications and games to enhance the performance of Android devices. New memory usage restrictions will be introduced on Google Play, requiring apps to adhere to specified memory thresholds, with potential consequences for non-compliance, including slowdowns, termination by the system, reduced visibility in the Google Play store, and publishing restrictions. Monitoring of compliance will begin in February 2027, following the introduction of memory limits with Android 17 on Pixel smartphones. This initiative is linked to a RAM shortage affecting the device market, with reports indicating that the base versions of the Pixel 11 Pro and Pixel 11 Pro XL have less RAM than their predecessors.