#Measure piper execution time

1 messages · Page 1 of 1 (latest)

bitter jungle
#

Where can I get more info about how long Piper takes to read a text?

I'm using the option to debug an voice assitant, and the raw log shows that Piper run in less than 0.3ms (diff between tts-start timestamp and tts-end) which I highly doubt. I'm running Piper as a HA add-on, both running inside a VM, hosted in a N100 CPUx4, with 16Gb RAM.

thin hedge
#

TTS messages are cached, so if it is a repeat of a prior request it probably came from the cache

#

otherwise would ned to look in the piper logs

#

think Piper doesn't log any of that by default until you turn on debug logging

bitter jungle
#

Already tried 😦 Changed the model to make sure it is not cached, still <1ms. Enabled debug logging, nothing in piper logs (just a bunch of periodic 'Sent info' lines). Enabled debug logging in Wyoming integration, but nothing in HA log.

thin hedge
#

did you try clearing tts cache?

#

and you'd probably need to check the addon logs, not core HA log

bitter jungle
#

I didn't, i assumed that new sentences and/or new modes was enough. Ill figure out how to clear it and try again

#

But nothing in the logs, not in addon or HA, despite having debugging enabled everywhere

bitter jungle
#

Ok, you were right. Enabling the debug log and cleaning the cache helps.

As suspected, the timestamps in the debug assistant UI are wrong, specifically tts-end. The debug log from the addon shows a more believable timestamp.

#

HA voice debug UI shows tts-end at 09:16:26.49, less than 1ms after tts-start

#

The addon log shows Piper ended processing the request at 09:16.37.36, about 860ms after it started.