HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

space at a much faster rate than the background poller would retrieve the information. The
registration occurs after scrolling in the device list stops for a short time. The devices are unregistered
after scrolling starts again.
NOTE With a single client, the updates to the visible devices should start happening quickly at a rate
consistent with the device list poller settings. With multiple clients, the updates should continue
to be regular, but with less frequency
Each object has a time threshold associated with it that allows HP Web Jetadmin to prevent a device
communication if it already has reasonably up-to-date information. If one client just asked for the
device description a minute ago, the threshold might cause that device communication to be skipped.
Device data is cached in the client to minimize additional communication with the server. Generally,
if a part of the UI requests device data, the client cache can prevent communication back to the
server.
Light (spikes in CPU usage during polling, dropping to negligible between polling)
Automatic groups
Automatic groups make use of the background poller. Any automatic group or filter group in the
system registers a set of requests from the device when polled. When HP Web Jetadmin detects
changes in the information being requested, it sends out a device changed event that causes groups
and filters to re-evaluate the device in question against the group or filter criteria.
Basic (no-policy) bound groups cause a slight increase in resource usage, but not a significant
amount. Increasing the number of groups populating at once and the number of devices going into
the groups does little more than extend the time taken to populate the groups.
Autogrouping with multiple policies, including an alert subscription, can dramatically increase
resource use. Large quantities of disk access can be caused by simultaneously reading the device
data from the database (to filter the devices), writing the new group membership to the database,
writing the content of the custom request to the database, and reading the alert eligibility information
from the device requests.
Fluctuating High
Report generation
Data collection is performed once per day and the amount of data collected fluctuates. Report
generation analyzes the data that is collected nightly and formulates reports for the user. Both of these
areas can cause Fluctuating High resource usage returning to Low as soon as the task is completed.
Fluctuating High
Device list export
Exporting devices can be defined to pull data only from the database or to pull all data from all
devices on-the-fly, so resource usage can vary. Large numbers of columns and devices can cause high
levels of resource usage during the duration of the device polling.
Fluctuating High to Severe High
Device configuration
Configuration occurs at a steady rate and never taxes the system above Fluctuating Moderate
resource usage. Some configuration items cause more overall network traffic than others, but resource
usage always remains low.
Light to Fluctuating Moderate