Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Google Android 17 is considering enabling 16KB page size: reducing app launch time by up to 30%
IT Home March 4 News, Tech media Android Authority today (March 4) published a blog post revealing that by digging into the Android 17 QPR1 Beta version and exploring the developer options, a “Use 16KB Page Size to Boot” feature was discovered. Enabling this feature can increase the minimum memory allocation unit from 4KB to 16KB.
IT Home quotes the blog post, explaining that computer page size is similar to the division of pages in a book. Android defaults to a 4KB page size, meaning memory is allocated in 4KB units. While this improves utilization, the CPU must manage millions of page tables, leading to high computational overhead.
Switching to a 16KB page size reduces the number of pages the CPU needs to track, thereby lowering access latency. Google estimates that enabling this feature shortens app startup time by 3% to 30%, and system boot time by 8%.
Due to early CPU architectures, Android systems have traditionally used 4KB pages. Early Android phones used 32-bit ARMv7 architecture, where the Memory Management Unit (MMU) design determined that 4KB pages were optimal, balancing address mapping and battery life.
It wasn’t until 2011, when the ARMv8 architecture introduced 64-bit support, that hardware gained the ability to flexibly configure 16KB or even 64KB pages, laying the foundation for current performance improvements.
Increasing the page size is not without costs; it can lead to increased internal memory fragmentation, causing some RAM to be wasted. Additionally, many older applications built with C language or NDK are designed around 4KB pages and need to be recompiled to support 16KB alignment.
Google has announced that starting from November 2025, all applications and updates submitted to Google Play targeting Android 15+ must support 16KB page size on 64-bit devices.