Merge pull request #262146 from anboisve/patch-24

Update stream-analytics-streaming-unit-consumption.md

Author: prmerger-automator[bot]

articles/stream-analytics/stream-analytics-streaming-unit-consumption.md

@@ -5,7 +5,7 @@ author: ahartoon
 ms.author: anboisve
 ms.service: stream-analytics
 ms.topic: conceptual
-ms.date: 11/14/2023
+ms.date: 01/02/2024
 ---
 # Understand and adjust Stream Analytics streaming units
 
@@ -26,9 +26,9 @@ The underlying compute power for V1 and V2 streaming units is as follows:
 For information on SU pricing, visit the [Azure Stream Analytics Pricing Page](https://azure.microsoft.com/pricing/details/stream-analytics/).
 
 ## Understand streaming unit conversions and where they apply
-There's an automatic conversion of Streaming Units which occurs from REST API layer to UI.  You may also notice this conversion in your [Activity log](stream-analytics-job-diagnostic-logs.md) where SU count appears different than the value which was specified on the UI for a particular job.  This is by design and it is because REST API fields must be limited to integer values and ASA jobs support fractional nodes (1/3 SUV2 and 2/3 SUV2).  To support this, we put an automatic conversion in place from Azure Portal to backend.  On the portal, you will see 1/3, 2/3, 1, 2, 3, … and so on.  In activity logs, REST API, etc. SU V2 values are 3, 7, 10, 20, 30, etc.  The backend structure is the proposal multiplied by 10 (rounding up in some cases).  This allows us to convey the same granularity and eliminate the decimal point at the API layer.  This conversion is automatic and has no impact on your job's performance.
+There's an automatic conversion of Streaming Units which occurs from REST API layer to UI (or Azure Portal).  You will notice this conversion in the [Activity log](stream-analytics-job-diagnostic-logs.md) as well where SU values appear different than the values on the Azure Portal.  This is by design, and the reason for it is because REST API fields are limited to integer values and ASA jobs support fractional nodes (1/3 and 2/3 Streaming Units).  Azure Portal displays node values 1/3, 2/3, 1, 2, 3, … etc, while Visual Studio Code, activity logs, and ASA's REST API layer display the same values multiplied by 10 as 3, 7, 10, 20, 30 respectively. 
 
-| Standard  | Standard V2 (UI) | Standard V2 (Backend) |
+| Standard  | Standard V2 (Azure Portal) | Standard V2 (Visual Studio Code, logs, Rest API) |
 | ------------- | ------------- | ------------- |
 | 1  | 1/3  | 3  |
 | 3  | 2/3  | 7  |
@@ -37,6 +37,7 @@ There's an automatic conversion of Streaming Units which occurs from REST API la
 | 18  | 3  | 30  |
 | ...  | ...  | ... |
 
+This allows us to convey the same granularity and eliminate the decimal point at the API layer.  This conversion is automatic and has no impact on your job's performance.
 
 ## Understand consumption and memory utilization
 To achieve low latency stream processing, Azure Stream Analytics jobs perform all processing in memory.  When running out of memory, the streaming job fails. As a result, for a production job, it’s important to monitor a streaming job’s resource usage, and make sure there's enough resource allocated to keep the jobs running 24/7.