HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

MoabDevice.MaxThreadPercentageUsedDuringStartup
25
The percentage of the overall MoabThreadPoolSize
that can be used during startup.
MoabDevice.MaxThreadPercentageUsedForPolling
25
The percentage of the overall MoabThreadPoolSize
that can be used for polling. Only the MOAB pollers
are affected. This setting affects all MOAB operations
(best bang for the buck). Any operation that requires
device communication (either GET or SET) benefit.
MoabDevice.MoabThreadPoolSize
30
Increasing this value might help improve performance
when performing actions across multiple devices.
NotificationManager.NumNotificationThreads
6
Used for processing and sending alerts. Increasing this
value might help if there are many active alert
subscriptions.
OxpmComponent.AlertThreads
5
Increasing this value might help if the OXPm client is
being used for alert notification for many devices.
SnmpTrapsReceiver.TrapsEventHandlerThreadCount
3
Increasing this value might help improve performance
if the HP Web Jetadmin instance receives a large
number of incoming traps (by user data collection,
alert subscriptions).
Tftp.TFTPThreadPoolCount
10
Increasing this value might help if firmware upgrades
are being performed on many HP Jetdirect NICs.
WebServer.Threads
5
Increasing this value might help if many HP Web
Jetadmin clients are being used simultaneously.
INCREASING FIRMWARE PERFORMANCE
The Firmware upgrade options screen under Tools, Options, Firmware allows for defining multiple
threads to perform firmware upgrades in a parallel fashion rather than serially under the Maximum
concurrent upgrades setting. The default setting is to upgrade eight devices simultaneously, although
this can be increased to 10 devices in a single task if desired. Firmware installation is faster when
multiple devices are upgraded at the same time, but more network traffic is generated. Operating
limitations might also restrict how many devices can receive upgrades simultaneously. This setting
applies to the number of devices inside a single task or multiple tasks. Ten tasks is the maximum
regardless.
If it is still taking too long to perform batch firmware upgrades, one additional technique can be used
to significantly decrease the time it takes to complete a batch upgrade process. There is a trade-off in
accuracy of reporting status, but the gains in time can be very significant.
The normal process for upgrading printer firmware involves opening a thread, sending the firmware
file through either a Port 9100 connection or Web Services connection, monitoring the upgrade status
on the device until it completes its power cycle and reports that the new firmware is in place, and then
closing the thread. If the maximum thread count is set to 10, after all 10 threads complete the
process, 10 more threads are attempted. This technique allows HP Web Jetadmin to very accurately
report success or failure. However, the constant status checking after delivering the firmware file can
take upwards of 90% of the total time to complete the process.
HP Web Jetadmin 10.3 SR2 and later allows for manipulating the FirmwareUpgrade.config.xml file to
bypass the status checking portion of the upgrade process. This means that HP Web Jetadmin delivers