Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve latency #3

Open
osteele opened this issue Feb 13, 2018 · 1 comment
Open

Improve latency #3

osteele opened this issue Feb 13, 2018 · 1 comment
Assignees
@osteele @newsch @SeunginLyu

Comments

@osteele
Copy link

osteele commented Feb 13, 2018

Bear's event → speech latency is high. (How high?) Improve this.

The SMS sequence is SMS → Twilio → Twilio Gateway → MQTT → sms_bear_gateway → MQTT → tts_worker. Any of these could be a hot spot. (Or, there could be several warm spots, and the chain is just too long.) The first step is to inspect where the latency is introduced.

The sequence is more complicated than it needs to be for particular applications. (It was designed to simplify in-class portion of the day one activity.) Now that we have some applications, we can optimize at the application level too.

Some of the work may apply to the Twilio Gateway project, rather than the code in the bear-as-a-service repo.
@osteele
Copy link
Author

osteele commented Feb 15, 2018

Some latency may just be warming the Heroku apps. This can be fixed by moving them to olin-build and paying the fee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@osteele osteele

@newsch newsch

@SeunginLyu SeunginLyu

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@osteele @newsch @SeunginLyu