RE: Opofiling to get the TIME STAMP

Hi William,

Thanks for the information shared. I will check the "-k"(--clockid) option

Regards,
Ramya

-----Original Message-----
From: William Cohen [mailto:[email protected]] 
Sent: Monday, September 28, 2015 8:24 PM
To: Ramya Shivalingamurthy -X (rshivali - INFOSYS LIMITED at Cisco); [email protected]; [email protected]
Subject: Re: Opofiling to get the TIME STAMP

On 09/28/2015 03:09 AM, Ramya Shivalingamurthy -X (rshivali - INFOSYS LIMITED at Cisco) wrote:
> Hi Team,
> 
>  
> 
> I am trying to use the Oprofiling tool to debug a high CPU issue. The output I am getting using the opreport gives the %age data of an API relative to other APIs at the time of profiling. This is not helping much to debug.
> 
>  
> 
> Can we get the time stamp for each samples/APIs which gets listed in the opreport output?
> 
>  
> 
> Please let me know if this can be done using the profile tool.
> 
>  
> 
> Thanks in advance,
> 
> Ramya
> 

Hi Ramya,

Oprofile was designed to show where the hot spots in code are. oprofile discards ordering information about the samples.  One doesn't know whether a particular sample was early in the data collection or late in the data collection.  The timestamp information isn't available in oprofile. Linux's perf stores each event in the perf.data file so you could get information about the order of the samples.  You might be able to use the "-k"(--clockid) to record more information when the sample is taken.  Maybe write a perf script (man perf-script) to analyze the resulting perf.data.

-Will

------------------------------------------------------------------------------