update

Author: mumian

articles/azure-resource-manager/troubleshooting/error-job-size-exceeded.md

@@ -3,7 +3,7 @@ title: Job size exceeded error
 description: Describes how to troubleshoot errors for job size exceeded or if the template is too large for deployments using a Bicep file or Azure Resource Manager template (ARM template).
 ms.topic: troubleshooting
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 11/07/2024
+ms.date: 11/11/2024
 ---
 
 # Resolve errors for job size exceeded
@@ -30,34 +30,18 @@ Other template limits are:
 - 64 output values
 - 24,576 characters in a template expression
 
-## Solution 1: Use dependencies carefully
+## Solution 1: Reduce name size
 
 # [Bicep](#tab/bicep)
 
-Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) that's created when a resource references another resource by its symbolic name. For most deployments, it's not necessary to use `dependsOn` and create an [explicit dependency](../bicep/resource-dependencies.md#explicit-dependency).
+Try to shorten the length of the names you use for [parameters](../bicep/parameters.md), [variables](../bicep/variables.md), and [outputs](../bicep/outputs.md). When these values are repeated in loops, a long name gets multiplied many times.
 
 # [JSON](#tab/json)
 
-When using [copy](../templates/copy-resources.md) loops to deploy resources, don't use the loop name as a dependency:
-
-```json
-dependsOn: [ "nicLoop" ]
-```
-
-Instead, use the instance of the resource from the loop that you need to depend on. For example:
-
-```json
-dependsOn: [
-    "[resourceId('Microsoft.Network/networkInterfaces', concat('nic-', copyIndex()))]"
-]
-```
+Try to shorten the length of the names you use for [parameters](../templates/parameters.md), [variables](../templates/variables.md), and [outputs](../templates/outputs.md). When these values are repeated through copy loops, a long name gets multiplied many times.
 
 ---
 
-Complex dependencies (a loop of n resources depending on a loop of n resources leads to us storing O(n * n) data rather each resource in a loop depending on its counterpart in the previous loop (O(n)). This one is surprising, but it adds up extremely fast.
-
-Complex dependencies can quickly consume the data limits. For example, if a loop of *n* resources depends on another loop of *n* resources, it results in storing *O(n²)* data. By contrast, if each resource in one loop only depends on its counterpart in the other loop, it results in *O(n)* data. This difference may seem subtle, but the storage impact grows very quickly.
-
 ## Solution 2: Simplify template
 
 # [Bicep](#tab/bicep)
@@ -66,38 +50,44 @@ When your file deploys lots of different resource types, consider dividing it in
 
 You can set other resources as implicit dependencies, and [get values from the output of modules](../bicep/outputs.md#outputs-from-modules).
 
+Use [template specs](../bicep/template-specs.md) rather than [Bicep modules](../bicep/modules.md). Bicep modules are converted into a single ARM template with nested templates.
+
 # [JSON](#tab/json)
 
 When your template deploys lots of different resource types, consider dividing it into [linked templates](../templates/linked-templates.md). Divide your resource types into logical groups and add a linked template for each group. For example, if you need to deploy lots of networking resources, you can move those resources to a linked template.
 
 You can set other resources as dependent on the linked template, and [get values from the output of the linked template](../templates/linked-templates.md#get-values-from-linked-template).
 
+Use [template specs](../templates/linked-templates.md#template-specs) rather than [nested templates](../templates/linked-templates.md#nested-template).
+
 ---
 
-## Solution 3: Reduce name size
+## Solution 3: Use dependencies carefully
 
 # [Bicep](#tab/bicep)
 
-Try to shorten the length of the names you use for [parameters](../bicep/parameters.md), [variables](../bicep/variables.md), and [outputs](../bicep/outputs.md). When these values are repeated in loops, a long name gets multiplied many times.
+Use an [implicit dependency](../bicep/resource-dependencies.md#implicit-dependency) that's created when a resource references another resource by its symbolic name. For most deployments, it's not necessary to use `dependsOn` and create an [explicit dependency](../bicep/resource-dependencies.md#explicit-dependency).
 
 # [JSON](#tab/json)
 
-Try to shorten the length of the names you use for [parameters](../templates/parameters.md), [variables](../templates/variables.md), and [outputs](../templates/outputs.md). When these values are repeated through copy loops, a long name gets multiplied many times.
-
----
-
-## Solution 4: Use template specs
-
-# [Bicep](#tab/bicep)
+When using [copy](../templates/copy-resources.md) loops to deploy resources, don't use the loop name as a dependency:
 
-Use [template specs](../bicep/template-specs.md) rather than [Bicep modules](../bicep/modules.md). Bicep modules are converted into a single ARM template with nested templates.
+```json
+dependsOn: [ "nicLoop" ]
+```
 
-# [JSON](#tab/json)
+Instead, use the instance of the resource from the loop that you need to depend on. For example:
 
-Use [template specs](../templates/linked-templates.md#template-specs) rather than [nested templates](../templates/templates/linked-templates.md#nested-template).
+```json
+dependsOn: [
+    "[resourceId('Microsoft.Network/networkInterfaces', concat('nic-', copyIndex()))]"
+]
+```
 
 ---
 
-## Solution 5: Reduce incompressible data
+Complex dependencies can quickly consume the data limits. For example, if a loop of *n* resources depends on another loop of *n* resources, it results in storing *O(n²)* data. By contrast, if each resource in one loop only depends on its counterpart in the other loop, it results in *O(n)* data. This difference may seem subtle, but the storage impact grows very quickly.
+
+## Solution 4: Reduce incompressible data
 
 Including large amounts of incompressible data, such as certificates or binaries, or data with a low compression ratio in a template or parameters will quickly consume the size limit.