diff --git a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
index c1c8ef2f8c..2292a7791e 100644
--- a/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
+++ b/windows/application-management/app-v/revision-heidi/appv-capacity-planning.md
@@ -550,16 +550,11 @@ Computers running the App-V client connect to the App-V publishing server to sen
>[!NOTE]
>The publishing server CPU usage is always high during the time interval when it must process simultaneous requests (>90% in most cases). The publishing server can handle ~1,500 client requests in one second.
-|Scenario|Variation|Number of App-V clients|Number of packages|Processor configuration on publishing server|Network connection type|Round trip time on the App-V client (in seconds)|CPU utilization on publishing server (in %)|
+|Scenario|Variation|Number of App-V clients|Number of packages|Processor configuration on publishing server|Network connection type|App-V client round-trip time (in seconds)|CPU utilization on publishing server (in %)|
|---|---|---|---|---|---|---|---|
-|App-V client sends publishing refresh request and receives response, each request containing 120 packages|Number of clients|100
1,000
5,000
10,000|120
120
120
120|Dual Core
Dual Core
Quad Core
Quad Core||||
-|Multiple packages in each refresh.|Number of packages|1,000
1,000|500
1,000|Quad Core||||
-|Network between client and publishing server.|1.5 Mbps Slow link network|100
500
1,000|120
120
120|Quad Core||||
-|||||||||
-|||||||||
-|||||||||
-|||||||||
-|||||||||
+|App-V client sends publishing refresh request and receives response, each request containing 120 packages|Number of clients|100
1,000
5,000
10,000|120
120
120
120|Dual Core
Dual Core
Quad Core
Quad Core|LAN|1
2
2
3|100<
99
89
77|
+|Multiple packages in each refresh.|Number of packages|1,000
1,000|500
1,000|Quad Core|LAN|2
3|92
91|
+|Network between client and publishing server.|1.5 Mbps Slow link network|100
500
1,000|120
120
120|Quad Core|1.5 Mbps intra-continental network|3
10 (0.2% failure rate)
7 (1% failure rate)||
@@ -712,6 +707,12 @@ Computers running the App-V client stream the virtual application package from t
* The size of the package being streamed.
* The available network bandwidth in your environment between the client and the streaming server.
+|Scenario|Summary|
+|---|---|
+|Multiple App-V clients stream applications from a single streaming server simultaneously.|If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.|
+|Size of the package being streamed.|The package size has a significant impact on the streaming/download time only for larger packages with a size of about 1 GB. For package sizes ranging from 3 MB to 100 MB, the streaming time ranges from 20 seconds to 100 seconds, with 100 simultaneous clients.|
+|Network between the App-V client and the streaming server.|Across a slow network (1.5 Mbps bandwidth), there is a 70–80% increase in response time compared to LAN (up to 100 users).|
+
@@ -752,6 +753,12 @@ Computers running the App-V client stream the virtual application package from t
The following table displays sample values for each of the factors in the previous list:
+|Scenario|Variation|Number of App-V clients|Size of each package|Network connection type|Round-trip time on the App-V client (in seconds)|
+|---|---|---|---|---|---|
+|Multiple App-V clients streaming virtual application packages from a streaming server.|Number of clients.|100
200
1,000
100
200
1,000|3.5 MB
3.5 MB
3.5 MB
5 MB
5 MB
5 MB|LAN|29
39
391
35
68
461|
+|Size of each package being streamed.|Size of each package.|100
200
100
200|21 MB
21 MB
109 MB
109 MB|LAN|33
83
100
160|
+|Network connection between client and App-V streaming server.|1.5 Mbps Slow link network.|100
100|3.5 MB
5 MB|1.5 Mbps intra-continental network|102
121|
+