From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753570AbbCYQ5l (ORCPT ); Wed, 25 Mar 2015 12:57:41 -0400 Received: from mail-ie0-f182.google.com ([209.85.223.182]:33959 "EHLO mail-ie0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752161AbbCYQ5h (ORCPT ); Wed, 25 Mar 2015 12:57:37 -0400 Message-ID: <5512E8FF.8030305@gmail.com> Date: Wed, 25 Mar 2015 10:57:35 -0600 From: David Ahern User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Joe Mario , Don Zickus CC: acme@kernel.org, linux-kernel@vger.kernel.org, Jiri Olsa Subject: Re: [PATCH] perf tool: Fix ppid for synthesized fork events References: <1426786875-18025-1-git-send-email-dsahern@gmail.com> <20150319205648.GC199787@redhat.com> <550B3A66.2030902@gmail.com> <20150324201020.GH199787@redhat.com> <5511D349.7070508@gmail.com> <5512A88A.1010608@redhat.com> In-Reply-To: <5512A88A.1010608@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/25/15 6:22 AM, Joe Mario wrote: > We ran "time perf mem record -a -e cpu/mem-loads,ldlat=50/pp -e > cpu/mem-stores/pp sleep 10" on a system that was running SPECjbb2013 in > the background. There were about 10,000 java threads with about 500 to > 800 in a runnable state at any given time. We ran it on a 4 socket x86 > IVB server. > > We had two perf binaries. One with your patch and one without it. > Because the benchmark doesn't always have a constant load, we ran the > above perf command in a loop alternating between the patched and > unpatched version. The elapsed wall clock times ("real" field from > time) for the perf with your patch was typically >= 50% longer than the > equivalent unpatched perf. Sent a v2 with performance numbers on my end. Adding -BN to the record removes processing of the events for build-ids. I also chose to use -e cpu-clock -F 1000 with -- usleep 1 to trim what perf-record is doing to *only* reading /proc files and generating COMM and FORK events. David