Open robert4os opened 2 years ago
Thank you for your detailed feedback. We are looking into the issue, and we will respond when we have more information.
@robert4os I have assigned the issue to the content author and SME @tedvilutis to evaluate and update as appropriate.
You can see available engine SKU options under Data Set category. It includes VMs with additional storage for cache.
@robert4os - It would be great if you share the full image, with the parameters too. D13s do have built in SSD that can be used for cache and therefore might be sufficient for the workload.
What is interesting is that the calculator logic always suggests choosing 2 16 cores over 4 8 cores. So it may be the case that you selected a specific value in the Engine SKU parameter. If you did, the calculator used the SSD available on the D13 to conclude you need 4 of them.
Hi,
this page refers to the use of the Data Explorer Cost Estimator https://dataexplorer.azure.com/AzureDataExplorerCostEstimator.html
Specifically under "Create ADX cluster" https://docs.microsoft.com/en-us/azure/time-series-insights/how-to-tsi-gen2-migration#create-adx-cluster ...it says to confirm the cost estimator's suggestion for cache, with an example 'Cost Estimator suggestion: 9x DS14 + 4 TB (cache)'
However (and this is the actual problem), the cost estimator does not make a suggestion as to the TB cache needed.
There is a paygo breakdown where the amount of cache could be deducted, but this is always 0 regardless of the input parameters.
best regards, Robert
[Enter feedback here]
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.