HPlogo Configuring and Managing MPE/iX Internet Services > Chapter 9 HP WebWise MPE/iX Secure Web Server

Performance

MPE documents

Complete PDF
Table of Contents
Glossary
Index

E0802 Edition 6 ♥
E0701 Edition 5
E0400 Edition 4

For best performance, files returned to the browser user should be in bytestream format. For example, .html, .htm, .shtml, .shtm, .txt, .gif, .jpeg, and .jpg files, should be in bytestream format instead of in MPE-type format. Bytestream files are more compatible with HP WebWise MPE/iX Secure Web Server and with other POSIX applications than are MPE-type files. If you have a web page that calls many images which are not in bytestream format (BA), you could have noticeable performance degradation.

If any of your files under the document root (htdocs) are either MPE fixed ASCII (FA), MPE variable ASCII (VA), or MPE variable binary (VB) files, you should consider converting them to bytestream files using the "tobyte" utility. Program files (fixed binary (FB) files with an NMPRG filecode) should never be converted.

A file's filetype can be determined using either the POSIX file command or the CI listfile command: 

  shell/iX> file index*.html
  index.html: MPE/iX 256-byte variable length binary (filecode: 0)
  index1.html: MPE/iX 80-byte fixed length ascii (filecode:0)

  shell/iX> callci listfile ./index.html,2
  PATH= /APACHE/PUB/htdocs/
  CODE ------------LOGICAL RECORD------- ----SPACE---- FILENAME
  
         SIZE  TYP     EOF   LIMIT R/B   SECTORS #X MX
         128W  VB       19  204800   1      32    1  8 index.html
          80B  FA       54  204800   1      32    1  8 index1.html
To convert an ASCII-type file (.htm*, .shtm*, or .txt), use the tobyte utility with the -at option. If it is a binary-type file (such as .jpeg, .jpg, or .gif), do not use the -at option:

tobyte -at /APACHE/PUB/htdocs/index.html /APACHE/PUB/htdocs/newindex.html

For more information on the "tobyte" utility, use the POSIX help facility (i.e., man tobyte).

If your HP WebWise MPE/iX Secure Web Server seems slow in responding, you might try running the HP WebWise MPE/iX Secure Web Server job stream file, JHTTPD, in the C queue instead of in the default D queue. The changes shown below allow HP WebWise MPE/iX Secure Web Server to run in the C queue while keeping the default execution level for jobs in the D queue. The jobpri command must be executed on the console or in a SYSSTART file.

!job jhttpd,mgr.apache,pub;pri=cs;outclass=,2

jobpri cs

Note that HP WebWise MPE/iX Secure Web Server consumes considerable CPU time at startup. If you elect to run HP WebWise MPE/iX Secure Web Server in the C queue, processes in the D and E queues may be starved while HP WebWise MPE/iX Secure Web Server is starting.



Troubleshooting

Working with Dynamic Shared Objects (DSOs)