On 2005.01.14, Bas Scheffers <[EMAIL PROTECTED]> wrote:
> Right, I have mine narrowed down to the following:
>
> With every static file served, memory usage goes up, but only once for
> every file. This happens both and in the same amount with direct serving
> and "ns_returnfile".
>
> To verify this, in my test I changed the filename in the HTML returned by
> my gallery script to something bogus ("foo.jpg.", instead of just
> "foo.jpg") resulting in many 404s, but no files returned. Everything else
> in my script was the same. (reading text files, setting global vars,
> ns_jpegsize, etc) With bogus files nsd stays <6MB, with real files, memory
> keeps growing, presumably untill every single static file has been served
> once.
>
> I don't have fastpath configured, but is there some other caching
> mechanism at work here?
What do you mean you don't have fastpath configured? By default, it's
on -- so if you don't have any fastpath configuration directives in your
config. file, that means you have fastpath cache turned on with a
default cache size of 5,120,000 bytes and 512,000 byte max entry size.
Try explicitly turning fastpath cache off, and see if your memory growth
behavior changes:
ns_section "ns/server/${servername}/fastpath"
ns_param cache off
nsd memory growth as the fastpath cache fills is totally expected. But,
the default cache size is ~5MB -- seeing the nsd grow to hundreds of MB
up to GB's in size is more than just fastpath cache filling, though.
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
