mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
Removed old tables.
This commit is contained in:
Heidi Lohr
@ -79,349 +79,23 @@ The following table describes each factor that impacts round-trip time in more d
|
|||||||
|The number of connection groups configured on the management server.|For up to 100 connection groups, there is no significant change in the round-trip response time on the publishing server. For 100–400 connection groups, there is a minor linear increase in the round-trip response time.|
|
|The number of connection groups configured on the management server.|For up to 100 connection groups, there is no significant change in the round-trip response time on the publishing server. For 100–400 connection groups, there is a minor linear increase in the round-trip response time.|
|
||||||
|The number of access groups configured on the management server.|For up to 40 access groups, there is a linear (approximately 3×) increase in the round-trip response time on the publishing server.|
|
|The number of access groups configured on the management server.|For up to 40 access groups, there is a linear (approximately 3×) increase in the round-trip response time on the publishing server.|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Factors impacting round-trip response time</th>
|
|
||||||
<th align="left">Description</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>The number of publishing servers simultaneously requesting package metadata refreshes.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>A single management server can respond to up to 320 publishing servers simultaneously requesting publishing metadata.</p></li>
|
|
||||||
<li><p>Round-trip response time for 320 pub servers is about 40 seconds.</p></li>
|
|
||||||
<li><p>For <50 publishing servers simultaneously requesting metadata, the round-trip response time is <5 seconds.</p></li>
|
|
||||||
<li><p>From 50 to 320 publishing servers, the response time increases linearly (approximately 2×).</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>The number of connection groups configured on the management server.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>For up to 100 connection groups, there is no significant change in the round-trip response time on the publishing server.</p></li>
|
|
||||||
<li><p>For 100–400 connection groups, there is a minor linear increase in the round-trip response time.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>The number of access groups configured on the management server.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>For up to 40 access groups, there is a linear (approximately 3×) increase in the round-trip response time on the publishing server.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V management server.
|
The following table displays sample values for each of the previous factors. In each variation, 120 packages are refreshed from the App-V management server.
|
||||||
|
|
||||||
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization|
|
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization|
|
||||||
|---|---|---|---|---|---|---|---|
|
|---|---|---|---|---|---|---|---|
|
||||||
|Publishing servers contact management server for publishing metadata at same time|0<br>0<br>0<br>0<br>0<br>0|1<br>1<br>1<br>1<br>1<br>1|50<br>100<br>200<br>300<br>315<br>320|LAN|5<br>10<br>19<br>32<br>30<br>37|17<br>17<br>17<br>15<br>17<br>15|
|
|Publishing servers contact management server for publishing metadata at same time|Number of publishing servers.|0<br>0<br>0<br>0<br>0<br>0|1<br>1<br>1<br>1<br>1<br>1|50<br>100<br>200<br>300<br>315<br>320|LAN|5<br>10<br>19<br>32<br>30<br>37|17<br>17<br>17<br>15<br>17<br>15|
|
||||||
|Publishing metadata contains connection groups|10<br>20<br>100<br>150<br>300<br>400|1<br>1<br>1<br>1<br>1<br>1|100<br>100<br>100<br>100<br>100<br>100|LAN|10<br>11<br>11<br>16<br>22<br>25|17<br>19<br>22<br>19<br>20<br>20|
|
|Publishing metadata contains connection groups|Number of connection groups|10<br>20<br>100<br>150<br>300<br>400|1<br>1<br>1<br>1<br>1<br>1|100<br>100<br>100<br>100<br>100<br>100|LAN|10<br>11<br>11<br>16<br>22<br>25|17<br>19<br>22<br>19<br>20<br>20|
|
||||||
|Publishing metadata contains access groups|0<br>0<br>0<br>0|1<br>10<br>20<br>40|100<br>100<br>100<br>100|LAN|10<br>43<br>153<br>535|17<br>26<br>24<br>24|
|
|Publishing metadata contains access groups|Number of access groups|0<br>0<br>0<br>0|1<br>10<br>20<br>40|100<br>100<br>100<br>100|LAN|10<br>43<br>153<br>535|17<br>26<br>24<br>24|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Variation</th>
|
|
||||||
<th align="left">Number of connection groups</th>
|
|
||||||
<th align="left">Number of access groups</th>
|
|
||||||
<th align="left">Number of publishing servers</th>
|
|
||||||
<th align="left">Network connection type publishing server/management server</th>
|
|
||||||
<th align="left">Round trip response time on the publishing server (in seconds)</th>
|
|
||||||
<th align="left">CPU utilization on management server</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Publishing servers simultaneously contacting management server for publishing metadata.</p></td>
|
|
||||||
<td align="left"><p>Number of publishing servers</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>50</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
<li><p>300</p></li>
|
|
||||||
<li><p>315</p></li>
|
|
||||||
<li><p>320</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>5</p></li>
|
|
||||||
<li><p>10</p></li>
|
|
||||||
<li><p>19</p></li>
|
|
||||||
<li><p>32</p></li>
|
|
||||||
<li><p>30</p></li>
|
|
||||||
<li><p>37</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>15</p></li>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>15</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Publishing metadata contains connection groups</p></td>
|
|
||||||
<td align="left"><p>Number of connection groups</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>10</p></li>
|
|
||||||
<li><p>50</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>150</p></li>
|
|
||||||
<li><p>300</p></li>
|
|
||||||
<li><p>400</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>10</p></li>
|
|
||||||
<li><p>11</p></li>
|
|
||||||
<li><p>11</p></li>
|
|
||||||
<li><p>16</p></li>
|
|
||||||
<li><p>22</p></li>
|
|
||||||
<li><p>25</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>19</p></li>
|
|
||||||
<li><p>22</p></li>
|
|
||||||
<li><p>19</p></li>
|
|
||||||
<li><p>20</p></li>
|
|
||||||
<li><p>20</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Publishing metadata contains access groups</p></td>
|
|
||||||
<td align="left"><p>Number of access groups</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>10</p></li>
|
|
||||||
<li><p>20</p></li>
|
|
||||||
<li><p>40</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>10</p></li>
|
|
||||||
<li><p>43</p></li>
|
|
||||||
<li><p>153</p></li>
|
|
||||||
<li><p>535</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
<li><p>26</p></li>
|
|
||||||
<li><p>24</p></li>
|
|
||||||
<li><p>24</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example, transactions/sec is approximately 30, batch requests approximately 200, and user connects approximately six.
|
The CPU utilization of the computer running the management server is around 25% irrespective of the number of publishing servers targeting it. The Microsoft SQL Server database transactions/sec, batch requests/sec and user connections are identical irrespective of the number of publishing servers. For example, transactions/sec is approximately 30, batch requests approximately 200, and user connects approximately six.
|
||||||
|
|
||||||
Using a geographically distributed deployment, where the management server and publishing servers utilize a slow link network between them, the round-trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
|
Using a geographically distributed deployment, where the management server and publishing servers utilize a slow link network between them, the round-trip response time on the publishing servers is within acceptable time limits (<5 seconds), even for 100 simultaneous requests on a single management server.
|
||||||
|
|
||||||
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization|
|
|Scenario|Variation|Number of connection groups|Number of access groups|Number of publishing servers|Network connection type|Round-trip response time (seconds)|Management server CPU utilization (in %)|
|
||||||
|---|---|---|---|---|---|---|---|
|
|---|---|---|---|---|---|---|---|
|
||||||
|Network connection between the publishing server and management server|1.5 Mbps Slow link Network|0<br>0|1<br>1|50<br>100|1.5 Mbps Cable DSL|4<br>5|1<br>2|
|
|Network connection between the publishing server and management server|1.5 Mbps Slow link Network|0<br>0|1<br>1|50<br>100|1.5 Mbps Cable DSL|4<br>5|1<br>2|
|
||||||
|Network connection between the publishing server and management server|LAN/WiFi Network|0<br>0|1<br>1|100<br>200|WiFi|11<br>20|15<br>17|
|
|Network connection between the publishing server and management server|LAN/WiFi Network|0<br>0|1<br>1|100<br>200|WiFi|11<br>20|15<br>17|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Variation</th>
|
|
||||||
<th align="left">Number of connection groups</th>
|
|
||||||
<th align="left">Number of access groups</th>
|
|
||||||
<th align="left">Number of publishing servers</th>
|
|
||||||
<th align="left">Network connection type publishing server/management server</th>
|
|
||||||
<th align="left">Round trip response time on the publishing server (in seconds)</th>
|
|
||||||
<th align="left">CPU utilization on management server</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Network connection between the publishing server and management server</p></td>
|
|
||||||
<td align="left"><p>1.5 Mbps slow link network</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>50</p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1.5 Mbps Cable DSL</p></li>
|
|
||||||
<li><p>1.5 Mbps Cable DSL</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>4</p></li>
|
|
||||||
<li><p>5</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>2</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Network connection between the publishing server and management server</p></td>
|
|
||||||
<td align="left"><p>LAN/WiFi network</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
<li><p>0</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Wifi</p></li>
|
|
||||||
<li><p>Wifi</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>11</p></li>
|
|
||||||
<li><p>20</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>15</p></li>
|
|
||||||
<li><p>17</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
|
Whether the management server and publishing servers are connected over a slow link network, or a high speed network, the management server can handle approximately 15,000 package refresh requests in 30 minutes.
|
||||||
|
|
||||||
## App-V Reporting Server capacity planning recommendations
|
## App-V Reporting Server capacity planning recommendations
|
||||||
@ -437,57 +111,13 @@ App-V clients send reporting data to the reporting server. The reporting server
|
|||||||
|Requests per second processed by the reporting server.|A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second. Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second, like a single reporting server, is about 127, with a max of 278 requests/second. A single reporting server can process 500 concurrent/active connections. A single reporting server can process a maximum 1,500 concurrent connections.|
|
|Requests per second processed by the reporting server.|A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second. Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second, like a single reporting server, is about 127, with a max of 278 requests/second. A single reporting server can process 500 concurrent/active connections. A single reporting server can process a maximum 1,500 concurrent connections.|
|
||||||
|Reporting database.|Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second. Throughput and response time are independent of database size.|
|
|Reporting database.|Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second. Throughput and response time are independent of database size.|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Summary</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Multiple App-V clients send reporting information to the reporting server simultaneously.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Round-trip response time from the reporting server is 2.6 seconds for 500 clients.</p></li>
|
|
||||||
<li><p>Round-trip response time from the reporting server is 5.65 seconds for 1000 clients.</p></li>
|
|
||||||
<li><p>Round-trip response time increases linearly depending on number of clients.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Requests per second processed by the reporting server.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>A single reporting server and a single database, can process a maximum of 139 requests per second. The average is 121 requests/second.</p></li>
|
|
||||||
<li><p>Using two reporting servers reporting to the same Microsoft SQL Server database, the average requests/second,like a single reporting server, is about 127, with a max of 278 requests/second.</p></li>
|
|
||||||
<li><p>A single reporting server can process 500 concurrent/active connections.</p></li>
|
|
||||||
<li><p>A single reporting server can process a maximum 1500 concurrent connections.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Reporting database.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Lock contention on the computer running Microsoft SQL Server is the limiting factor for requests/second.</p></li>
|
|
||||||
<li><p>Throughput and response time are independent of database size.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
### Calculating random delay
|
### Calculating random delay
|
||||||
|
|
||||||
The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
|
The random delay specifies the maximum delay (in minutes) for data to be sent to the reporting server. When the scheduled task is started, the client generates a random delay between **0** and **ReportingRandomDelay** and will wait the specified duration before sending data.
|
||||||
|
|
||||||
Random delay = 4 \* number of clients / average requests per second. (CHECK)
|
Random delay = 4 * number of clients/average requests per second.
|
||||||
|
|
||||||
Example: For 500 clients, with 120 requests per second, the Random delay is, 4 \* 500 / 120 = about 17 minutes. (CHECK)
|
Example: Random delay for 500 clients with 120 requests per second is 4 * 500/120 = about 17 minutes.
|
||||||
|
|
||||||
## App-V publishing server capacity planning recommendations
|
## App-V publishing server capacity planning recommendations
|
||||||
|
|
||||||
@ -495,7 +125,6 @@ Computers running the App-V client connect to the App-V publishing server to sen
|
|||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>The following list displays the main factors to consider when setting up the App-V publishing server:
|
>The following list displays the main factors to consider when setting up the App-V publishing server:
|
||||||
|
|
||||||
* The number of clients connecting simultaneously to a single publishing server.
|
* The number of clients connecting simultaneously to a single publishing server.
|
||||||
* The number of packages in each refresh.
|
* The number of packages in each refresh.
|
||||||
* The available network bandwidth in your environment between the client and the App-V publishing server.
|
* The available network bandwidth in your environment between the client and the App-V publishing server.
|
||||||
@ -506,47 +135,6 @@ Computers running the App-V client connect to the App-V publishing server to sen
|
|||||||
|Number of packages in each refresh.|Increasing number of packages will increase response time by about 40% (up to 1,000 packages).|
|
|Number of packages in each refresh.|Increasing number of packages will increase response time by about 40% (up to 1,000 packages).|
|
||||||
|Network between the App-V client and the publishing server.|Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1,000 users).|
|
|Network between the App-V client and the publishing server.|Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1,000 users).|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Summary</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Multiple App-V clients connect to a single publishing server simultaneously.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>A publishing server running dual core processors can respond to at most 5000 clients requesting a refresh simultaneously.</p></li>
|
|
||||||
<li><p>For 5,000–10,000 clients, the publishing server requires a minimum quad core.</p></li>
|
|
||||||
<li><p>For 10,000–20,000 clients, the publishing server should have dual quad cores for more efficient response times.</p></li>
|
|
||||||
<li><p>A publishing server with a quad core can refresh up to 10,000 packages within three seconds. (Supports 10,000 simultaneous clients.)</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Number of packages in each refresh.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Increasing number of packages will increase response time by about 40% (up to 1,000 packages).</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Network between the App-V client and the publishing server.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Across a slow network (1.5 Mbps bandwidth), there is a 97% increase in response time compared to LAN (up to 1,000 users).</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
>[!NOTE]
|
>[!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 about 1,500 client requests in one second.
|
>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 about 1,500 client requests in one second.
|
||||||
|
|
||||||
@ -556,153 +144,12 @@ Computers running the App-V client connect to the App-V publishing server to sen
|
|||||||
|Multiple packages in each refresh.|Number of packages|1,000<br>1,000|500<br>1,000|Quad Core|LAN|2<br>3|92<br>91|
|
|Multiple packages in each refresh.|Number of packages|1,000<br>1,000|500<br>1,000|Quad Core|LAN|2<br>3|92<br>91|
|
||||||
|Network between client and publishing server.|1.5 Mbps Slow link network|100<br>500<br>1,000|120<br>120<br>120|Quad Core|1.5 Mbps intra-continental network|3<br>10 (0.2% failure rate)<br>7 (1% failure rate)||
|
|Network between client and publishing server.|1.5 Mbps Slow link network|100<br>500<br>1,000|120<br>120<br>120|Quad Core|1.5 Mbps intra-continental network|3<br>10 (0.2% failure rate)<br>7 (1% failure rate)||
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
<col width="12%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Variation</th>
|
|
||||||
<th align="left">Number of App-V clients</th>
|
|
||||||
<th align="left">Number of packages</th>
|
|
||||||
<th align="left">Processor configuration on the publishing server</th>
|
|
||||||
<th align="left">Network connection type publishing server/App-V client</th>
|
|
||||||
<th align="left">Round trip time on the App-V client (in seconds)</th>
|
|
||||||
<th align="left">CPU utilization on publishing server (in %)</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>App-V client sends publishing refresh request & receives response, each request containing 120 packages</p></td>
|
|
||||||
<td align="left"><p>Number of clients</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
<li><p>5,000</p></li>
|
|
||||||
<li><p>10,000</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Dual core</p></li>
|
|
||||||
<li><p>Dual core</p></li>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1</p></li>
|
|
||||||
<li><p>2</p></li>
|
|
||||||
<li><p>2</p></li>
|
|
||||||
<li><p>3</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>99</p></li>
|
|
||||||
<li><p>89</p></li>
|
|
||||||
<li><p>77</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Multiple packages in each refresh</p></td>
|
|
||||||
<td align="left"><p>Number of packages</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>500</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>2</p></li>
|
|
||||||
<li><p>3</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>92</p></li>
|
|
||||||
<li><p>91</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Network between client and publishing server</p></td>
|
|
||||||
<td align="left"><p>1.5 Mbps slow link network</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>500</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
<li><p>120</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
<li><p>Quad core</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1.5 Mbps intra-continental network</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>3</p></li>
|
|
||||||
<li><p>10 (with 0.2% failure rate)</p></li>
|
|
||||||
<li><p>17 (with 1% failure rate)</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
## App-V streaming capacity planning recommendations
|
## App-V streaming capacity planning recommendations
|
||||||
|
|
||||||
Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
|
Computers running the App-V client stream the virtual application package from the streaming server. Round trip response time is measured on the computer running the App-V client, and is the time taken to stream the entire package.
|
||||||
|
|
||||||
>[!IMPORTANT]
|
>[!IMPORTANT]
|
||||||
>The following list identifies the main factors to consider when setting up the App-V streaming server:
|
>The following list identifies the main factors to consider when setting up the App-V streaming server:
|
||||||
|
|
||||||
* The number of clients streaming application packages simultaneously from a single streaming server.
|
* The number of clients streaming application packages simultaneously from a single streaming server.
|
||||||
* The size of the package being streamed.
|
* The size of the package being streamed.
|
||||||
* The available network bandwidth in your environment between the client and the streaming server.
|
* The available network bandwidth in your environment between the client and the streaming server.
|
||||||
@ -713,44 +160,6 @@ Computers running the App-V client stream the virtual application package from t
|
|||||||
|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.|
|
|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).|
|
|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).|
|
||||||
|
|
||||||
<table>
|
|
||||||
<colgroup>
|
|
||||||
<col width="50%" />
|
|
||||||
<col width="50%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Summary</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Multiple App-V clients stream applications from a single streaming server simultaneously.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>If the number of clients simultaneously streaming from the same server increases, there is a linear relationship with the package download/streaming time.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Size of the package being streamed.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>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.</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Network between the App-V client and the streaming server.</p>
|
|
||||||
<p></p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>Across a slow network (1.5 Mbps bandwidth), there is a 70–80% increase in response time compared to LAN (up to 100 users).</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
The following table displays sample values for each of the factors in the previous list:
|
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)|
|
|Scenario|Variation|Number of App-V clients|Size of each package|Network connection type|Round-trip time on the App-V client (in seconds)|
|
||||||
@ -759,131 +168,6 @@ The following table displays sample values for each of the factors in the previo
|
|||||||
|Size of each package being streamed.|Size of each package.|100<br>200<br>100<br>200|21 MB<br>21 MB<br>109 MB<br>109 MB|LAN|33<br>83<br>100<br>160|
|
|Size of each package being streamed.|Size of each package.|100<br>200<br>100<br>200|21 MB<br>21 MB<br>109 MB<br>109 MB|LAN|33<br>83<br>100<br>160|
|
||||||
|Network connection between client and App-V streaming server.|1.5 Mbps Slow link network.|100<br>100|3.5 MB<br>5 MB|1.5 Mbps intra-continental network|102<br>121|
|
|Network connection between client and App-V streaming server.|1.5 Mbps Slow link network.|100<br>100|3.5 MB<br>5 MB|1.5 Mbps intra-continental network|102<br>121|
|
||||||
|
|
||||||
<table style="width:100%;">
|
|
||||||
<colgroup>
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
<col width="16%" />
|
|
||||||
</colgroup>
|
|
||||||
<thead>
|
|
||||||
<tr class="header">
|
|
||||||
<th align="left">Scenario</th>
|
|
||||||
<th align="left">Variation</th>
|
|
||||||
<th align="left">Number of App-V clients</th>
|
|
||||||
<th align="left">Size of each package</th>
|
|
||||||
<th align="left">Network connection type streaming server/App-V client</th>
|
|
||||||
<th align="left">Round trip time on the App-V client (in seconds)</th>
|
|
||||||
</tr>
|
|
||||||
</thead>
|
|
||||||
<tbody>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Multiple App-V clients streaming virtual application packages from a streaming server.</p></td>
|
|
||||||
<td align="left"><p>Number of clients.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
<li><p>1,000</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>3.5 MB</p></li>
|
|
||||||
<li><p>3.5 MB</p></li>
|
|
||||||
<li><p>3.5 MB</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>5 MB</p></li>
|
|
||||||
<li><p>5 MB</p></li>
|
|
||||||
<li><p>5 MB</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>29</p></li>
|
|
||||||
<li><p>39</p></li>
|
|
||||||
<li><p>391</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>35</p></li>
|
|
||||||
<li><p>68</p></li>
|
|
||||||
<li><p>461</p></li>
|
|
||||||
</ul></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="even">
|
|
||||||
<td align="left"><p>Size of each package being streamed.</p></td>
|
|
||||||
<td align="left"><p>Size of each package.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p>200</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>21 MB</p></li>
|
|
||||||
<li><p>21 MB</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>109</p></li>
|
|
||||||
<li><p>109</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
<li><p>LAN</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<p>33</p>
|
|
||||||
<p>83</p>
|
|
||||||
<p></p>
|
|
||||||
<p>100</p>
|
|
||||||
<p>160</p></td>
|
|
||||||
</tr>
|
|
||||||
<tr class="odd">
|
|
||||||
<td align="left"><p>Network connection between client and App-V streaming server.</p></td>
|
|
||||||
<td align="left"><p>1.5 Mbps slow link network.</p></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>100</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>3.5 MB</p></li>
|
|
||||||
<li><p></p></li>
|
|
||||||
<li><p>5 MB</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<ul>
|
|
||||||
<li><p>1.5 Mbps intra-continental network</p></li>
|
|
||||||
</ul></td>
|
|
||||||
<td align="left"><p></p>
|
|
||||||
<p>102</p>
|
|
||||||
<p></p>
|
|
||||||
<p>121</p></td>
|
|
||||||
</tr>
|
|
||||||
</tbody>
|
|
||||||
</table>
|
|
||||||
|
|
||||||
Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
|
Each App-V streaming server should be able to handle a minimum of 200 clients concurrently streaming virtualized applications.
|
||||||
|
|
||||||
>[!NOTE]
|
>[!NOTE]
|
||||||
|
|||||||
Reference in New Issue
Block a user