Re:What's wrong with 1975 programming
by jacquesm on Wednesday July 28, 2010 @05:28PM
(#1555741)
Currently serving up billions of images per day from memory images that are more than 100 times the available physical memory (and there's plenty of that).
Small objects can be batched in to a single page at the application level, the VM will then move these in and out of the resident pool as one unit.
The operating system uses elevator sorting and knows enough about the disk that it will attempt to sequentially invalidate pages.
The assumption is not that the working set will fit (mostly) in to RAM, the assumption is that a page fault is a relatively rare occurrence and that other threads will not be stalled by the IO done for one. It is the changes to the working set that determine page faults, not the size of the total set.
On my boxes I solved one issue with this (and the maximum number of systemwide sockets) by running a varnish instance for every physical CPU in the machines.
Small objects can be batched in to a single page at the application level, the VM will then move these in and out of the resident pool as one unit.
The operating system uses elevator sorting and knows enough about the disk that it will attempt to sequentially invalidate pages.
The assumption is not that the working set will fit (mostly) in to RAM, the assumption is that a page fault is a relatively rare occurrence and that other threads will not be stalled by the IO done for one. It is the changes to the working set that determine page faults, not the size of the total set.
On my boxes I solved one issue with this (and the maximum number of systemwide sockets) by running a varnish instance for every physical CPU in the machines.