Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Mar 20, 2024

Permanent way for increasing resources for speech-cr-stt-am-patcher deployment

Client need to apply speech patches every time Speech service upgrade issue(requires uninstall and install). To reduce the effort, client log tickets to get a permanent way tor speech patches.

We get response from Speech team: 

Unfortunately there isn't a good permanent solution for this right now. TemporaryPatches which are used in WA and WD are not possible in Speech as Speech doesn't use the oppy framework.

While it is possible to modify the cpu/ephemeral storage/memory values, it is not straightforward to do so as the limits depend on the requests. And we did confirm that changes to the am-patcher configmap (i.e. increasing the number of threads) are overwritten by the Speech operator. As such, we believe the best solution for now is to apply the workaround when needed for larger AM training jobs. After training is successful, the speech operator can be scaled back up until the next training job.

We are planning some improvements / design changes to AM training in the near future -- we will take these shortcomings into consideration during that process.

 

Idea priority High