-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Reduce Costs by Minimizing Service Usage or Deactivation When Not Needed or in Idle #2022
Comments
How about deploying with minimal costs(Use the free tier of Azure AI Search). Have you considered trying that? |
@bnodir Thank you for your suggestion! While I’m happy to pay for the services I use (as the free tier’s limits and performance don’t meet my needs), my main concern is the cost incurred when the service is idle, such as during nights and weekends. My original question was about finding a way to avoid these idle-time costs—for example, by automatically shutting down or minimizing the service during these periods, and then re-enabling it within 10-20 minutes when needed. Deleting and redeploying resources isn’t practical in my case, as I manage a large volume of documents. The redeployment process would take significant time and add further costs due to the digest process. Do you have any suggestions that could address this issue? |
@YIN-Renlong - For the digest process, I recommend using local PDF/CSV parsers if your documents are in those formats. However, I agree that redeployment is not the best option due to the time it consumes. |
@bnodir Thanks for the suggestions. I would be more than willing to explore the option of deploying the app locally and utilizing the API only when necessary. However, I am concerned about whether this approach might impact performance, especially during more demanding tasks. I am very interested in a solution that focuses on local deployment as much as possible, as there are many scenarios where continuous online deployment isn't required. Minimizing the usage of cloud resources could significantly help reduce costs. However, from what I can see, this project doesn't seem to have a branch or pathway that fully supports local deployment yet, right? I would really appreciate hearing more of your thoughts or recommendations on this approach. Looking forward to your insights. |
Is there a feature comparison between localpdf parser and Azure Document Intelligence? What shall a at all not always use the local pdf parser? |
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
azd version?
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: