Sign in to follow this  
Big Buck Hunter

New long block standard

Recommended Posts

4KB page swapping will be superseded. CPU's and OS are moving to larger virtual memory pages (eg. 4MB) and thus 4KB HD sectors would still generate multi-sector write request per page.

Need to have small files grouped together to reduce space waste when using larger cluster size.

Wouldn't that increase memory slack space enormously? Each DLL, EXE and other memory mapped file would use a size rounded up to the nearest 4 mb?

Share this post


Link to post
Share on other sites
4KB page swapping will be superseded. CPU's and OS are moving to larger virtual memory pages (eg. 4MB) and thus 4KB HD sectors would still generate multi-sector write request per page.

Need to have small files grouped together to reduce space waste when using larger cluster size.

Wouldn't that increase memory slack space enormously? Each DLL, EXE and other memory mapped file would use a size rounded up to the nearest 4 mb?

Yes it would, if only 4MB pages were being used.

As I understand it, both large and small page sizes can be used at once. E.g. in Linux the default will still be the small (4K, 8K) page size but apps that are mmap'ing big chunks of memory can request larger page sizes. This is a nice gain for large DB apps on 64bit machines.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this