On Fri, Feb 3, 2017 at 2:55 PM, Simon Farnsworth <simon...@fb.com> wrote:
> We already capture start and exit times in the external wrapper process - > so your added detail of measuring "useful work" (in addition to "total > time") tells us if we're seeing a huge overhead in setup/teardown of > Mercurial. > I think you might have missed a bit of crucial detail. If Mercurial sits for 100 minutes after writing its output to the pager before the user quits the pager, that's not going to show up as I/O time with your scheme, but it is going to show up as elapsed time. This is why capturing that measuring elapsed time is not useful. There's an indeterminate amount of time where literally nothing is happening (it's not teardown, and it's not overhead, it's just waiting for the pager) that you need to be able to discount.
_______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
