Scalability Of The Primary Server; Infrastructure Scale Assumptions; Section 3.2, "Scalability Of The Primary Server; Section 3.1.3, "Infrastructure Scale Assumptions - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

3.1.3 Infrastructure Scale Assumptions

The following scale assumptions should be made when building the design of the infrastructure.
These actual scale assumptions might be different, based on the services you are providing and how
you break up the services across multiple servers.
ZENworks Primary Server: A single ZENworks Primary Server can provide all ZENworks
services (content, collection, and configuration) for as many as 3,000 devices in a ZENworks
Management Zone.
This is based on a Primary Server handling approximately 1,000 concurrent connections for all
service types (content, configuration, and content).
This is not real-world; see
additional details on how these figures can change, and what you need to consider to ensure
that you are scaling to meet the needs of the organization.
Server-grade Satellite device: A single ZENworks Satellite (dedicated server) can provide
content services for as many as 1,000 concurrent devices.
This is not real-world; see
additional details on how these figures can change, and what you need to consider to ensure
that you are scaling to meet the needs of the organization.
Workstation-grade Satellite device: A single ZENworks Satellite (dedicated workstation)
can provide content services for as many as 250 concurrent devices.
This is not real-world; see
additional details on how these figures can change, and what you need to consider to ensure
that you are scaling to meet the needs of the organization.

3.2 Scalability of the Primary Server

Understanding the scalability of the individual components that make up the ZENworks
infrastructure is of the greatest importance. You need to understand the limitations and where you
can expect to see performance degradation to ensure that you build an infrastructure that can
perform well, regardless of the load that your end-user community places on it.
The first area that you need to consider is the scalability of the Primary Server. It is important to
design your Primary Server placement based on the information you collected during your
assessment phase and what you anticipate your overall design will require. You should design your
infrastructure so that there are always Primary Servers available to service devices and the
administrators that are managing the system.
The following sections contain more information:
Section 3.2.1, "Factors Influencing Scalability," on page 26
Section 3.2.2, "Load Testing in the Novell SuperLab," on page 26
Section 3.2.3, "Achieving Scalability in the Real World," on page 29
Section 3.2, "Scalability of the Primary Server," on page 25
Section 3.3, "Scalability of Satellite Devices," on page 30
Section 3.3, "Scalability of Satellite Devices," on page 30
Gathering Critical Information for Design Activities
for
for
for
25