Achieving Scalability In The Real World - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

This test environment stretched the limits of what the ZENworks Configuration Management
system is able to achieve, giving us a good idea of where the system starts to reach its limitations. It
comes close to a real-world simulation.
Tests and results.
Table 3-1
Test Name
BOE Report
Inventory Report
Policy
Multicast
Bundle
When the server is under load, and we created an MSI bundle and assigned it to 60 devices, there is
a large increase in the amount of time it takes to complete the task. In this situation, it is
recommended that you have a dedicated server for ZENworks Control Center so that there would be
virtually no impact on performance.
The ZENworks Control Center is used by administrators to perform administrative tasks, including
the management of content within the system. For environments that are managed by a small
number of administrators (one or two), accessing ZENworks Control Center from a Primary Server
that is also performing work might not be cause performance issue. For larger implementations
(several thousand devices, large amounts of daily content activity, and several administrators),
having a dedicated Primary Server in place for ZENworks Control Center resolves potential
performance issues.

3.2.3 Achieving Scalability in the Real World

Section 3.2.2, "Load Testing in the Novell SuperLab," on page 26
SuperLab to determine the limits of the ZENworks system. Scalability, on the other hand, is
achieved through the proper placement of services, a well thought-out design, and the proper
configuration of services within the ZENworks Configuration Management system itself.
Test Description
Run Predefined BOE
report - Bundle
Deployment Status (313
pages)
Run canned report
"Devices By Machine /
Login Name"
Create policy, assign it to
60 devices, and perform
a quicktask on all 60
devices to get the policy
Create Multicast bundle
and multicast to 60
devices
Create an MSI Bundle of
OpenOffice, assign it to
60 devices, and refresh
all 60 by using a
quicktask
Primary Server Under No
Load
15 seconds
7 seconds
7 minutes 43 seconds
4 minutes 20 seconds
25 minutes 30 seconds
discussed testing in the Novell
Gathering Critical Information for Design Activities
Primary Server Under
Load
18 seconds
8 seconds
7 minutes 45 seconds
4 minutes 27 seconds
1 hour 10 minutes 17
seconds
29