HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

Disk
Another performance consideration is the disk subsystem. If the database runs from a very slow disk,
performance is affected. Also, the disk should be defragmented periodically to make sure the files are
in a good state. Use drive, Properties, Tools, Defragmentation to determine if the drive needs to be
defragmented.
CONCURRENT USER LOGIN
HP Web Jetadmin is a client/server application, which means that the client can run on a different
machine than the server. The majority of the work is contained and managed by the server. Multiple
clients can be connected to the same server. A client connects to the server and uses the .NET
remoting channel to communicate. There are two types of communication that occur between the
client and the server: client-driven requests and events from the server.
A client makes requests to the server in response to user actions or server events. This starts when the
user launches the client. The client establishes a connection with the server, retrieves updates, and
gets any information from the server needed to launch the UI. As the user uses the application, the
client requests data from the server or requests work to be done by the server as necessary. This traffic
is generally very predictable as it is a direct result of work the user wants.
HP Web Jetadmin is architected for multiple-user access. The application is designed to support 15 or
more concurrent connections while maintaining a high degree of performance. Of course, application
usage makes the performance at each client vary somewhat depending on the client load and the
hardware hosting the application. The hardware and software requirements should be considered
when the application is loaded with multiple and simultaneous user connections. An example would
be where one user is tasked with discovering all devices in the enterprise while at the same time
another user is tasked with establishing groups and generating reports. In this case, on a slower host,
HP Web Jetadmin might exhibit slow performance when large reports are being generated and
discoveries are being run at the same time. System resources, network bandwidth, and other factors
have an impact on how well the software performs under these conditions.
APPLICATION PERFORMANCE
HP Web Jetadmin processes large amounts of data while allowing users to work productively. When
users view device lists or access device configuration or status details, HP Web Jetadmin spends CPU
bandwidth on multiple device data retrieval. In addition, the application collates and communicates
device information back to multiple client sessions. An observant administrator can use tools such as
Microsoft Performance Monitor to view the results of this background processing. Here are some
characteristics about performance and the HP Web Jetadmin software:
 During background task executions, the application might consume a high percentage of the
host’s processor for only short durations of time.
 Consumption of the system processor might be pronounced on host systems that meet only
minimum hardware requirements.
 Consumption of the system processor might be pronounced on single host systems that run both
the HP Web Jetadmin application and the client application on the same host.
 Performance gains can be realized with HP Web Jetadmin running on multiple processor systems.
HP Web Jetadmin relies on network traffic to keep the information displayed to the user reasonably
up-to-date. HP Web Jetadmin carefully makes numerous tradeoffs to balance network traffic with up-to-
date information and performance.