Response time too long


#1

When I use the monitor (HDMI) on RP-3 I can see that there is a log entry on the screen of my wakeup word, possible 1 or 2 minutes later. Almost at the same time, I can already read the answer. However, the till I receive actually a voice takes another minute or two.
Is there something to set?


#2

First of all, I don’t know where you are located but there might be a fair bit of latency hitting api.mycroft.ai. Also, on the PiCroft image I’ve noticed a performance decrease (as opposed to our mark 1 unit, which is also using a pi 3 but with a custom sound card). It also might have something to do with the tailing of log files, not sure.


#3

I have the same problem. Whats the solution?


#4

I am in Taiwan.

traceroute mycroft.ai
traceroute to mycroft.ai (45.55.42.41), 30 hops max, 60 byte packets
1 192.168.178.1 (192.168.178.1) 0.319 ms 0.482 ms 0.677 ms
2 60-251-143-254.HINET-IP.hinet.net (60.251.143.254) 3.077 ms 3.223 ms 3.227 ms
3 tpe4-3301.hinet.net (168.95.210.78) 2.797 ms 3.017 ms 3.026 ms
4 220-128-11-250.HINET-IP.hinet.net (220.128.11.250) 3.390 ms 220-128-11-222.HINET-IP.hinet.net (220.128.11.222) 13.512 ms 220-128-11-250.HINET-IP.hinet.net (220.128.11.250) 3.384 ms
5 tpdt-3011.hinet.net (220.128.5.122) 9.061 ms TPDT-3011.hinet.net (220.128.1.110) 6.138 ms TPDT-3012.hinet.net (220.128.4.82) 5.719 ms
6 r4101-s2.tp.hinet.net (220.128.7.117) 4.336 ms r4101-s2.tp.hinet.net (220.128.3.253) 3.286 ms 2.984 ms
7 r4001-s2.tp.hinet.net (220.128.12.5) 4.373 ms 4.602 ms r4001-s2.tp.hinet.net (220.128.12.1) 2.014 ms
8 r11-pa.us.hinet.net (211.72.108.201) 143.305 ms r11-pa.us.hinet.net (211.72.108.225) 124.180 ms r11-pa.us.hinet.net (211.72.108.153) 125.594 ms
9 r12-pa.us.hinet.net (202.39.83.46) 142.168 ms r12-pa.us.hinet.net (202.39.83.78) 142.185 ms 136.756 ms
10 sjo-b21-link.telia.net (195.12.255.205) 132.129 ms 126.851 ms 145.359 ms
11 nyk-bb4-link.telia.net (213.155.133.238) 217.144 ms nyk-bb4-link.telia.net (80.91.254.176) 214.717 ms nyk-bb4-link.telia.net (213.155.130.130) 213.778 ms
12 nyk-b3-link.telia.net (80.91.248.174) 200.630 ms nyk-b3-link.telia.net (80.91.247.21) 200.386 ms nyk-b3-link.telia.net (62.115.123.5) 205.147 ms
13 digitalocean-ic-306498-nyk-b3.c.telia.net (62.115.45.10) 216.884 ms 216.637 ms digitalocean-ic-306497-nyk-b3.c.telia.net (62.115.45.6) 201.492 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

The log file on screen shows a response time from less then 1 sec between the recognized question and the answer. I take that as fast Internet connection. The waiting time, till the wakeup word is recognized and the question understood, with 1 to 2 minutes, simple too long. There must be some problem.

Since the system has upgraded to 0.83 I get 99% no answer anymore. “Sorry, I could not catch that” after a randomly time, even if I have not even asked something.


#5

Hi saw your post, as a musician I use the ‘low latency’ linux kernel in ubuntu studio as a lot of audio applications don’t work properly without it, also user group memory allocation is something to be considered with linux audio! don’t know if this is any help? but thought I would respond anyway, have a cool day there.


#6

What power supply are you using with your pi?

I did some experimentation yesterday with a Pi having the same problem and found a better power supply solved the problem.

I’m going to test with the recommend power supply this weekend (which puts out 2Amps) and see if that needs to be what we recommend.