You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I come from a research team which works on bugs in real-world applications.
I want to make a report about a few potential performance improvement in your project.
In file examples/google-voicekit-snippets-mark/cloudspeech_demo.py, synthesize_speech is called to generate audio files in each run. However, its input is a (or from a set of) fixed string. This behavior increases execution time and brings unnecessary service cost. A caching mechanism could help such situation, e.g. save audio file on disk at first API call, and re-use that file later.
Perhaps someone might be able to confirm if these seem reasonable. Also, if you need any help, I'm happy to provide some code snippet for fixing.
If you are not offended by it, we may include your response as a percentage number (e.g. xx% of applications faces xx problem, and xx% of them confirms it) in our research paper.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
I come from a research team which works on bugs in real-world applications.
I want to make a report about a few potential performance improvement in your project.
In file
examples/google-voicekit-snippets-mark/cloudspeech_demo.py
,synthesize_speech
is called to generate audio files in each run. However, its input is a (or from a set of) fixed string. This behavior increases execution time and brings unnecessary service cost. A caching mechanism could help such situation, e.g. save audio file on disk at first API call, and re-use that file later.Perhaps someone might be able to confirm if these seem reasonable. Also, if you need any help, I'm happy to provide some code snippet for fixing.
If you are not offended by it, we may include your response as a percentage number (e.g. xx% of applications faces xx problem, and xx% of them confirms it) in our research paper.
Thanks.
The text was updated successfully, but these errors were encountered: