[Kwiver-users] Time logging in KWIVER

[Paul Tunison]

We should generally not be using wall clock timing for performance
measurement.

On Wed, Nov 15, 2017 at 11:35 AM, Matt Brown <matt.brown at kitware.com> wrote:

> Do we have or can we decide on a standard practice for logging processing
> time debug. I have gotten into the habit of wrapping the _step in my
> processes with
>
> kwiver::vital::wall_timer timer;
> timer.start();
> ...
> timer.stop();
> double elapsed_time = timer.elapsed();
> LOG_DEBUG( logger(), "Elapsed time detecting objects: " << elapsed_time );
>
> Some questions:
>
>    - Should this be TRACE or DEBUG?
>    - Should we should wall and/or CPU timing?
>    - Will all of this be superseded by a more-unified framework that does
>    this automatically?
>
> Best,
> Matt
>
> _______________________________________________
> Kwiver-users mailing list
> Kwiver-users at public.kitware.com
> http://public.kitware.com/mailman/listinfo/kwiver-users
>
>


-- 
Paul Tunison
Senior R&D Engineer
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065 USA

Phone: (518) 371-3971 Ext.164
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/kwiver-users/attachments/20171115/685d4313/attachment.html>