-
Notifications
You must be signed in to change notification settings - Fork 497
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.
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
Pipeline init taking around 10 seconds with daily + rtvi #1052
Comments
Hey @markbackman , I noticed that the daily.co APIs seem to be a bit slow for the Indian region. We’re hosting our servers in Mumbai, and each API call, like creating a room, getting a token, or joining a room, takes around 1 second or more. Do you have any idea why this might be happening? |
@Vaibhav-Lodha, the REST APIs are hosted in us-west-2, so that would explain some of the latency (~170ms roundtrip). Note that all media is geolocated, so once your room is created, your connecting to a media server in Mumbai. That still doesn't explain the 10 second delay. Is this repeatable? |
Yes @markbackman it happens in every event, and have also pointed the room creation to mumbai still no help :( |
There is no room creation in Mumbai. Room creation is always us-west-2. We have team members in India and Asia Pacific. I'll see if they encounter a similar issue. |
@markbackman did we get a chance to have a word with indian team? |
He did run the demo, but used Daily Prebuilt. I've asked him to run again using an RTVI client, so that the data is more like-for-like. |
RTVI + Daily.co transport Issue
I am using gemini bot example but with TTS + STT + LLM instead of gemini multi-modal but for some reason the entire init process is taking 10+ seconds in each run and not able to figure out where can i save time, i am thinking to try threading instead of process but i believe that wont change much of things.
Pipecat Version - 0.0.52
Python - 3.12
The text was updated successfully, but these errors were encountered: