Journey / Chirp HD TTS is very slow to respond... ~ 4,000ms. Not a production ready API from google.

[KevinParker372]

So, for a single sentence I'm getting latencies of nearly 3,000ms... Is this normal? I've noticed Google quality just constantly in the decline the past few years.

Not sure how I can work with an API that takes 3,950ms to complete. I've compared the data in the API Service details and they match internal times (ruling out DNS). The actual response from Google takes this long.

[cassandramae]

Hi @KevinParker372,

Welcome to Google Cloud Community!

Thanks for your feedback. I understand your concern regarding the latency you're experiencing with the Text-to-Speech API. Having a delay of ~4000ms for a single sentence is unacceptable. With this, I recommend filing this using the issue tracker so our engineers could look into it. You may also check this documentation on what to expect after you've opened an issue.

Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.

[gaieges]

I've had some very slow response times on the TTS endpoints as of late as well, it seems like it's only started in the past few days but almost all of the voices take upwards of 1m to generate 6 words.

@cassandramae 

[gaieges]

I've concluded that while some of the Journey voices work still, they just dont have the capacity dedicated to them that they used to.  I'm switching over to similar sounding Chirp voices instead.