Frequent slow speech synthesis or ResourceExhausted: "No free synthesizer" responses

Question

DWinkler 51

In recent days we're often receiving very slow synthesis or ResourceExhausted: "No free synthesizer" responses.

The health pages do not indicate any problems, is there a way to find the cause of this issue? (region is westeurope)

Kind regards,
Daniel

GiftA-MSFT 11,176 Reputation points

2022-03-19T04:05:30.357+00:00

Hi, thanks for reaching out. Is this a free/paid subscription? Also, where exactly are you viewing this error, Azure Service Health?
DWinkler 51 Reputation points

2022-03-21T07:39:32.41+00:00

Thanks for your feedback, it is the paid subscription.
I am getting this error as result from the synthesis service on a normal SSML request.
Sometimes the synthesis peeks to approx 15 seconds; when the next, similar request is returning in <1 sec.
(The health endpoint reports all green.)
GiftA-MSFT 11,176 Reputation points

2022-03-28T18:44:16.123+00:00

Thanks for the information. Following up to inquire on whether you're still experiencing this issue? I'm unable to reproduce this issue in my environment. If issue persists, my recommendation is to raise a support request so engineers can perform proper diagnosis of the issue. Sorry for any inconvenience.

Your answer

GiftA-MSFT 11,176 Reputation points

2022-03-19T04:05:30.357+00:00

Hi, thanks for reaching out. Is this a free/paid subscription? Also, where exactly are you viewing this error, Azure Service Health?
DWinkler 51 Reputation points

2022-03-21T07:39:32.41+00:00

Thanks for your feedback, it is the paid subscription.
I am getting this error as result from the synthesis service on a normal SSML request.
Sometimes the synthesis peeks to approx 15 seconds; when the next, similar request is returning in <1 sec.
(The health endpoint reports all green.)
GiftA-MSFT 11,176 Reputation points

2022-03-28T18:44:16.123+00:00

Thanks for the information. Following up to inquire on whether you're still experiencing this issue? I'm unable to reproduce this issue in my environment. If issue persists, my recommendation is to raise a support request so engineers can perform proper diagnosis of the issue. Sorry for any inconvenience.