Re: Tips regarding measuring function execution times

[Graham Bloice <graham.bloice () trihedral com>]

Visual Studio

On 14 October 2017 at 15:18, Paul Offord <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

___________________________________________________________________________
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