HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

Test Plan Strategy—Scenario Matrix
 At the completion of these scenarios, there is a matrix applied that entails each system performing
the various operations (Discovery, Alerts, Data Collections) simultaneously with a slowly
increasing load that mirrors the ramp of the individual scenarios (one with a device list of 1,100
and the other with a device list of 3,900 = 16* subnet).
Completed Discovery
 Discovery—Imported list of 1,100 devices
Result = Success
 Discovery—Run Full Subnet through Templates with each portion being smaller than a Class B
Network
Result = Success
Completed Alerts
 Alerts—(1,100 devices) General Alerts: 100 to Max
Result = Success
 Alerts—(4,000 devices) General Alerts: 100 to Max
Result = Success
Completed Data Collection
 Data Collection—(1,100 devices) All except Hourly Peak Usage: 100 to Max
Result = Success
 Data Collection, Hourly Peak Usage—(1,100 devices) Data Collection: 100 to Max
Result = Success
 Data Collection—(4,000 devices) All except Hourly Peak Usage: 100 to Max
Result = Success
Completed Remote DB with SSD
 Data Collection—(4,000 devices) SSD Remote DB, All except Hourly Peak Usage: 100 to Max
Result = Success
 Alerts—(4,000 devices) SSD Remote DB, General Alerts: 100 to Max
Result = Success
 Data Collection—(4,000 devices) SSD Remote DB, Hourly Peak Usage: 100 to Max
Result = Success
Conclusions
 Individual tasks, no matter how intensive, do not cause issues for HP Web Jetadmin when running
on 64-bit systems if the device list is limited to approximately 1,100 devices.
 System-intensive tasks, such as Hourly Peak Usage, can be successfully applied to 1,100 devices
with no adverse reactions in HP Web Jetadmin, including responsiveness of the client, even when
the client runs on the same host.
 When device lists of 4,000 devices are used, individual tasks slow performance only at the client,
but do not cause system losses (for example, crashes).
 The only limitation on a system with 1,100 devices is when simultaneously applying a large Alert
subscription and creating a large Data Collection. This can cause the client to become
temporarily unresponsive. In this case, the server continues to run without interruption.
As a result of these tests, one might conclude that a system in full usage can support roughly 4,000
devices or more. Remember, this is a system that is being used with many HP Web Jetadmin features
activated. Can one HP Web Jetadmin server support more than 4,000 devices? Absolutely. However,
the answer also depends on how you load features and devices as well as the types of features and