On Sat, Jan 25, 2003 at 05:38:08PM -0800, Sean O'Rourke wrote: > The problem's actually _virtual_ memory use/fragmentation, not physical > memory or swap. Say you map in 10k small files -- that's 640M virtual > memory, just over a fourth of what's available. Now let's say you're also > using mmap() in your webserver to send large (10M) files quickly over the > network. The small files, if they're long-lived get scattered all over > VA-space, so there's a non-trivial chance that the OS won't be able to > find a 10MB chunk of free addresses at some point.
Yeah, but in pratice, most, if not all the small files will mapped in at startup. It's no different than the situation at the moment on Solaris where XS modules require the .so object to be mmapped in. > Weird, I know, but that's why it stuck in my mind. You have to map quite > a few files to get this to happen, but it's a real possibility with a > 32-bit address space and a long-running process that does many small > mmap()s and some large ones. But we'll all be using 64-bit processors by the time parrot's released :-) -- This email is confidential, and now that you have read it you are legally obliged to shoot yourself. Or shoot a lawyer, if you prefer. If you have received this email in error, place it in its original wrapping and return for a full refund. By opening this email, you accept that Elvis lives.
