<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Linus should chime in here. There is an instrumentation framework for exactly this sort of pipeline timing analysis. Linus know the most about this.<div class=""><br class=""></div><div class="">—Matt</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 15, 2017, at 12:48 PM, Matt Brown <<a href="mailto:matt.brown@kitware.com" class="">matt.brown@kitware.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">We should generally not be using wall clock timing for performance measurement.</div></blockquote><div class=""><br class=""></div><div class="">Aren't there instances where wall clock time is relevant (e.g., total latency)? In a pipeline, where processing gets blocked until something finishes, it can be helpful to identify bottle necks.<br class=""></div></div><br class=""></div></div>
_______________________________________________<br class="">Kwiver-users mailing list<br class=""><a href="mailto:Kwiver-users@public.kitware.com" class="">Kwiver-users@public.kitware.com</a><br class="">http://public.kitware.com/mailman/listinfo/kwiver-users<br class=""></div></blockquote></div><br class=""></div></body></html>