From owner-freebsd-current@FreeBSD.ORG Fri Dec 2 18:27:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01C45106566B for ; Fri, 2 Dec 2011 18:27:24 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200:216:3eff:fe2c:dc8f]) by mx1.freebsd.org (Postfix) with ESMTP id C270D8FC12 for ; Fri, 2 Dec 2011 18:27:23 +0000 (UTC) Received: from [172.25.0.9] ([96.54.172.165]) (authenticated bits=0) by orthanc.ca (8.14.4/8.14.4) with ESMTP id pB2IRMMq070266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2011 10:27:23 -0800 (PST) (envelope-from lyndon@orthanc.ca) Date: Fri, 2 Dec 2011 10:27:21 -0800 (PST) From: Lyndon Nerenberg To: Ryan Stone In-Reply-To: Message-ID: References: <20111202015133.GA4111@dragon.NUXI.org> <20111202064132.GC88903@troutmask.apl.washington.edu> <4ED8776F.9060301@FreeBSD.org> <20111202072349.GA89183@troutmask.apl.washington.edu> <20111202083501.GA73959@dragon.NUXI.org> User-Agent: Alpine 1.10 (OSX 962 2008-03-14) Organization: The Frobozz Magic Homing Pigeon Company MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: WITHOUT_PROFILE=yes by default X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2011 18:27:24 -0000 > In this case, 'obsolete' means it's a difficult-to-use tool that > requires recompiling your application, can't be used in production, > doesn't work when shared libraries are in the picture, offers > limited-to-no visibility into the underlying reasons why a particular > code path is a hotspot and introduces large measurement errors No, it just means it doesn't work for you. It does work for me, though. And for many others. Many a time I have shipped a profiled binary off to a customer site to determine where they are having performance problems. This works because they don't need to install any third-party tools or jump through other hoops. It's not perfect, but it is a useful debugging tool. The arguments I keep hearing here are "I don't (understand how to effectively) use this tool, therefore it should be removed." Collectively that argument can be applied to each and every component of FreeBSD when taken across the entire user base. Thus we can infinately optimize the builds though 'rm -rf /usr/src'. Now can we please just leave WITHOUT_PROFILE alone and go fix real bugs? If it will help, I will toss in a few hundred bucks to help Max buy a faster build machine. --lyndon