Wireshark mailing list archives
Re: Tips regarding measuring function execution times
From: Paul Offord <Paul.Offord () advance7 com>
Date: Thu, 19 Oct 2017 07:14:27 +0000
Thanks Graham, I wasn’t aware of that. The hot path concept is the same as I get from PerfView but I may need to get even more granular, i.e. code blocks rather than functions, hence the interest in timers. I also thought that timing would give me a cross check. I plan to look into Guy’s suggestion regarding CPU time – as he says, I only need relative values. I’ll try to find some time this weekend. Best regards…Paul From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Graham Bloice Sent: 16 October 2017 11:11 To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] Tips regarding measuring function execution times Visual Studio On 14 October 2017 at 15:18, Paul Offord <Paul.Offord () advance7 com<mailto:Paul.Offord () advance7 com>> wrote: I’m investigating a performance problem with the TRANSUM dissector. I’d like to measure the accumulated time taken to execute a function in a Release build. My basic idea is to do something like this: guint32 execute_time_us; . . start_stopwatch(&execute_time_us); function_call_to_be_measured(); pause_stopwatch(&execute_time_us); . . . stop_and_output_stopwatch(&execute_time_us); Is there a standard way to do this in Wireshark? How can I output the accumulated time on, say, the Status Line? Best regards…Paul Visual Studio (Pro at least, not sure about Community), includes profiling tools, both sampling (less accurate, but least invasive) and instrumented (more accurate, more invasive). See here for starters: https://msdn.microsoft.com/en-us/library/ms182372.aspx -- Graham Bloice ______________________________________________________________________ This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Tips regarding measuring function execution times, (continued)
- Re: Tips regarding measuring function execution times Paul Offord (Oct 15)
- Re: Tips regarding measuring function execution times Roland Knall (Oct 15)
- Re: Tips regarding measuring function execution times Paul Offord (Oct 15)
- Re: Tips regarding measuring function execution times Roland Knall (Oct 15)
- Re: Tips regarding measuring function execution times Guy Harris (Oct 16)
- Re: Tips regarding measuring function execution times Peter Wu (Oct 16)
- Re: Tips regarding measuring function execution times Helge Kruse (Oct 16)
- Re: Tips regarding measuring function execution times Paul Offord (Oct 19)