I was under the impression that page size was determined by the hardware. If that's not the case, then why don't they just push it as high as they can that still makes sense. A lot of devices these days have upwards of 8GB of RAM, so it would make more sense to push it higher than 16KB. I'd push for at least 64KB. It's not like too many programs need a granularity below that anyway. How many allocator implementations take chunks that small anyhow.
16KB is often chosen as a compromise between these various factors. It provides a balance that works well across a wide range of applications and hardware configurations. While some systems do use larger pages (like 64KB or even 2MB in some cases), the standard page size tends to stick to something that offers a good balance between reducing fragmentation, maximizing TLB efficiency, and maintaining compatibility with existing software. In conclusion, while increasing page size can make sense in some contexts (and indeed, some systems and applications do use larger pages), it isn’t always the best solution for general-purpose computing. The 16KB size is often a “sweet spot” that balances the trade-offs effectively for most scenarios.
I was under the impression that page size was determined by the hardware. If that's not the case, then why don't they just push it as high as they can that still makes sense. A lot of devices these days have upwards of 8GB of RAM, so it would make more sense to push it higher than 16KB. I'd push for at least 64KB. It's not like too many programs need a granularity below that anyway. How many allocator implementations take chunks that small anyhow.
16KB is often chosen as a compromise between these various factors. It provides a balance that works well across a wide range of applications and hardware configurations. While some systems do use larger pages (like 64KB or even 2MB in some cases), the standard page size tends to stick to something that offers a good balance between reducing fragmentation, maximizing TLB efficiency, and maintaining compatibility with existing software.
In conclusion, while increasing page size can make sense in some contexts (and indeed, some systems and applications do use larger pages), it isn’t always the best solution for general-purpose computing. The 16KB size is often a “sweet spot” that balances the trade-offs effectively for most scenarios.