Choosing capacity for your QnA Maker deployment
The QnA Maker service, takes a dependency on three Azure resources:
- App Service (for the runtime)
- Azure Search (for storing QnAs)
- App Insights (optional, for storing chat logs and telemetry)
Before you create your QnA Maker service, you should decide which tier of the above services is appropriate for you.
Typically there are three parameters you need to consider:
The throughput you need from the service: Select the appropriate App Plan for your App service based on your needs. You can scale up or down the App. This should also influence your Azure Search SKU selection, see more details here.
Size and the number of knowledge bases: Choose the appropriate Azure search SKU for your scenario. You can publish N-1 knowledge bases in a particular tier, where N is the maximum indexes allowed in the tier. Also check the maximum size and the number of documents allowed per tier.
For example, if your tier has 15 allowed indexes, you can publish 14 knowledge bases (1 index per published knowledge base). The fifteenth index is used for all the knowledge bases for authoring and testing.
Number of documents as sources: The free SKU of the QnA Maker management service limits the number of documents you can manage via the portal and the APIs to 3 (of 1 MB size each). The standard SKU has no limits to the number of documents you can manage. See more details here.
The following table gives you some high-level guidelines.
|QnA Maker Management||App Service||Azure Search||Limitations|
|Experimentation||Free SKU||Free Tier||Free Tier||Publish Up to 2 KBs, 50 MB size|
|Dev/Test Environment||Standard SKU||Shared||Basic||Publish Up to 14 KBs, 2 GB size|
|Production Environment||Standard SKU||Basic||Standard||Publish Up to 49 KBs, 25 GB size|
For upgrading your QnA Maker stack, see Upgrade your QnA Maker service.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.