From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Size of perf data files Date: Mon, 05 Jan 2015 21:39:49 -0800 Message-ID: <87ppas31sq.fsf@tassilo.jf.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mga01.intel.com ([192.55.52.88]:42056 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751281AbbAFFjt (ORCPT ); Tue, 6 Jan 2015 00:39:49 -0500 In-Reply-To: (Yale Zhang's message of "Mon, 5 Jan 2015 19:21:22 -0800") Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Yale Zhang Cc: linux-perf-users@vger.kernel.org Yale Zhang writes: > Perf developers, > I'm also very interested in reducing the size of the data files when > reporting call stacks. Currently, profiling 30s of execution with call The simplest way is to lower the frequency. Especially don't use adaptive frequency (which is the default). This also lowers overhead quite a bit. Also don't use dwarf unwinding. It is very expensive. There are some other ways. I suspect you would most of what you want by just running a fast compressor (snappy or LZO) at perf record time. That would be likely a useful addition. -Andi -- ak@linux.intel.com -- Speaking for myself only