> If you see the process size grow with the file, then it > is probably because your system is configured to use > mmap() for sending files, and your system happens to > show the size of a mapped file as part of the process size. > > That memory is _NOT_ actually used once per proxy and it > is shared between processes and automatically allocated and > freed by the OS as part of its buffer cache as necessary, > just like normal file caching.
That makes sense... I didn't think of something like that since I assumed that an OS wouldn't fill all available real memory with buffer cache blocks. I'm not enough of a kernel/libc person to know that much about mmap... it seems to me from what you say that it would be apache using mmap to send the files. Or would it be part of the open syscall? I'd like to stop it from doing that, if possible. Thanks... Josh Beck [EMAIL PROTECTED]
