<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Nov 6, 2015, at 12:53 PM, Evan Jones <<a href="mailto:ejones@twitter.com" class="">ejones@twitter.com</a>> wrote:<div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 6, 2015 at 3:45 PM, Jason Evans <span dir="ltr" class=""><<a href="mailto:jasone@canonware.com" target="_blank" class="">jasone@canonware.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">No, dumps are always based on the most recent stats reset (process start or "prof.reset" mallctl call). You can view incremental differences between two dumps by using the --base option to jeprof.<br class=""></blockquote><div class=""><br class=""></div><div class="">Is this true if you use opt.lg_prof_interval? Then what is the point of the opt.prof_accum option?</div></div></div></div></div></blockquote><div><br class=""></div><div>opt.lg_prof_interval is merely a dump triggering mechanism. opt.prof_accum controls whether cumulative stats are collected at all.</div><br class=""></div><div>Jason</div><br class=""></body></html>