Skip to main content
Skip table of contents

Using MEASURE Counters

LightWave Server supports several 'user defined' MEASURE counters which you can use to help analyze performance of your LightWave Server application. The available MEASURE counter names and types are shown below:


Counter Name

Type

Description

lw-connect

qbusy

The amount of time spent processing an inbound connection.

lw-conn-ssl-hs

qbusy

The amount of time spent processing the SSL/TLS handshake for a connection.

lw-request

qbusy

The amount of time spent receiving the request from the client over the network.

lw-deserialize

qbusy

The amount of time spent deserializing the request payload into the server request IPM.

lw-pathsend-io

qbusy

The amount of time spent sending the request and receiving the reply from a Pathway server.

lw-process-io

qbusy

The amount of time spent sending the request and receiving the reply from a process server.

lw-serialize

qbusy

The amount of time spent serializing the reply IPM into the response payload.

lw-request

qbusy

The amount of time spent sending the response to the client over the network

lw-diag-log

qbusy

The amount of time spent generating the diagnostic log.

lw-msg-log

qbusy

The amount of time spent filtering and delivering the message logging events.

lw-requests

accum

The total number of requests processed

lw-ssl-hs

accum

The total number of SSL/TLS handshakes

lw-recv-bytes

accum

The total number of bytes received over the network

lw-send-bytes

accum

The total number of bytes received over the network

lw-sock-recvs

accum

The total number of TCP/IP socket recv operations processed

lw-sock-sends

accum

The total number of TCP/IP socket send operations processed

lw-sock-connects

accum

The total number of TCP/IP connection requests processed.

lw-sock-accepts

accum

The total number of TCP/IP accept operations processed.

lw-deleg-fails

accum

The total number of SERVER to SWORKER requests delegations that have failed. This may indicate that the SWORKERs are over capacity.

lw-pathsend-ios

accum

The total number of Pathsend I/Os processed.

lw-process-ios

accum

The total number of process server I/Os processed.

lw-pathsend-max

snapshot

The maximum number of concurrent Pathsend I/O operations

lw-process-max

snapshot

The maximum number of concurrent process server I/O operations.



TEXT
> VOLUME <lwc-installation-subvolume>
> MEASCOM

+ add processh server

+ add userdef server
+ add counter lw-connect        , process server, qbusy
+ add counter lw-conn-ssl-hs    , process server, qbusy
+ add counter lw-request        , process server, qbusy
+ add counter lw-deserialize    , process server, qbusy
+ add counter lw-pathsend-io    , process server, qbusy
+ add counter lw-process-io     , process server, qbusy
+ add counter lw-serialize      , process server, qbusy
+ add counter lw-response       , process server, qbusy
+ add counter lw-diag-log       , process server, qbusy
+ add counter lw-msg-log        , process server, qbusy
+ add counter lw-requests       , process server, accum
+ add counter lw-ssl-hs         , process server, accum
+ add counter lw-recv-bytes     , process server, accum
+ add counter lw-send-bytes     , process server, accum
+ add counter lw-sock-recvs     , process server, accum
+ add counter lw-sock-sends     , process server, accum
+ add counter lw-sock-connects  , process server, accum
+ add counter lw-sock-accepts   , process server, accum
+ add counter lw-deleg-fails    , process server, accum
+ add counter lw-pathsend-ios   , process server, accum
+ add counter lw-process-ios    , process server, accum
+ add counter lw-pathsend-max   , process server, snapshot
+ add counter lw-process-max    , process server, snapshot

+ start measurement LWSMEAS

== run your application

+ stop measurement LWSMEAS

+ list userdef *, rate off


These MEASURE counters may differ from values recorded in diagnostic logs. The diagnostic log measures elapsed time whereas the MEASURE counters represent actual work time.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.