Per, Thanks for the info. I remember I was seeing the ram usage by varnishncsa did not change a lot. I didn't take any screen shot, so I may remember wrong. Let me try it one more time and see what happened. Could it be the log dumping to disk can't keep up with the insertion rate, so varnish has to allocate more for the in-memory logging? Just a guess.
thanks, Zheng On Fri, Sep 28, 2012 at 6:46 AM, Per Buer <[email protected]>wrote: > Hi, > > On Thu, Sep 27, 2012 at 5:47 PM, Zheng Liu <[email protected]> wrote: > >> Hi, >> >> I tried to use varnishncsa to generate log on disk, so I can have another >> daemon tail and analyze it. However, when I enable it, I see varnishd >> starts to use more and more memory. I am using varnish-3.0.3 on Ubuntu >> 11.10. The box has 190G and I configured varnish to use 160G. Its footprint >> has been stable at 180G for months. Then after I started varnishncsa, >> within 5 hours, all the memory was gone and it starts to use swap. I wonder >> if this is expected behavior, and we are suppose to allow more head room >> during logging with varnishncsa? >> > > There have been some reports of a varnishleak in varnishncsa - but in the > cases I've seen it's varnishncsa itself which balloons up. Would that be > the case here aswell? > > -- > Per Buer > Phone: +47 21 98 92 61 / Mobile: +47 958 39 117 / Skype: per.buer > *Varnish makes websites fly!* > Whitepapers <http://www.varnish-software.com/whitepapers> | > Video<http://www.youtube.com/watch?v=x7t2Sp174eI> | > Twitter <https://twitter.com/varnishsoftware> > > >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
