Date: Thu, 26 Jan 2006 19:02:17 -0800 From: Jason Evans <jasone@FreeBSD.ORG> To: Andrey Chernov <ache@FreeBSD.ORG> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/stdlib malloc.c Message-ID: <6B47D688-0A7D-421F-9830-9493EC375307@FreeBSD.ORG> In-Reply-To: <20060127025150.GA57825@nagual.pp.ru> References: <200601270236.k0R2ai2x067283@repoman.freebsd.org> <20060127025150.GA57825@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 26, 2006, at 6:51 PM, Andrey Chernov wrote: > I worry about my system performance. Could you please make all > statistics > and debug code conditional, debending on some flags which could be > set as > malloc options? Even in case this is a test period now, some people > perhaps don't want some tests. It is much easy to turn some tests > off via > malloc options than to comment out manually corresponding malloc.c > defines > after each cvsup. Unfortunately, run-time checks for the debugging features are expensive, since the debugging code is scattered throughout malloc.c. This pretty much mandates compile-time configuration, for performance reasons. I can disable statistics and debugging, if there's a general consensus to do so. How much performance difference is the debug/ stats code making for you? I've only been disabling debug/stats for benchmarking purposes, so I don't have a good feel for how much it impacts overall system performance. Thanks, Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B47D688-0A7D-421F-9830-9493EC375307>