Overhead when enabling debug?
mat999 at gmail.com
Sun Sep 29 11:59:22 UTC 2013
Thank you agentz, that looks amazing. I will be including that in the next
server software push.
And also Maxim, thank you for you for taking the time to prepare those
figures. I am going to my own testing and presuming that holds with our
usecase / modules I will be deploying --with-debug myself. Its definitely
worth it for <5% any day.
On Sat, Sep 28, 2013 at 5:01 AM, Yichun Zhang (agentzh)
<agentzh at gmail.com>wrote:
> On Fri, Sep 27, 2013 at 6:16 AM, mex wrote:
> > i have a question regarding the --with-debug - option; do i have to
> > much overhead,
> > when compiling nginx with that option, but have it disabled per default?
> We avoid enabling debug logs in production because when we really need
> to debug online issues, debug logs are just too expensive to emit and
> analyze (consider the box is currently experiencing an L7 attack).
> Also, --with-debug compiles in extra code paths which *could* have
> bugs and consume some extra CPU cycles even when you're not further
> enabling it in nginx.conf.
> Also, you'll never never have enough debug logs for answer those
> really hard questions in production.
> We only enable it for every day Nginx related development. For online
> trouble shooting, we're relying on systemtap to do low overhead
> dynamic tracing on various software stack levels, as demonstrated by
> my Nginx Systemtap Toolkit:
> and also all those samples in my stap++ project:
> Hope these help.
> Best regards,
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx