Jorijn: "response times this run tanked", and then, sharply, "are you sure its
back? or has it always been like this."
It has always been like this, and the number was never measuring the daemon. The
client's wall clock starts when the verify request starts, so it includes however
long the user takes to get a finger onto the sensor. In the run that prompted the
question the slow presses spent two seconds and more watching an EMPTY sensor --
ten consecutive frames at metric 129 to 142 against a 133 idle floor -- and then
matched on the very first frame that had contact in it.
Every matched press in that run reads "press 1: 1 frames -> MATCH". Not one
needed a retry. The presses that felt instant were the ones where a finger was
already down when the request started, and the presses that felt slow were the
ones where it was not.
So the loop now times from first contact as well as from the start, and says so
in as many words. A figure that silently includes human reaction time cannot be
compared between runs, between people, or against a phone.
Jorijn van der Graaf
eb50e5b6fb