dxpresto(8X)dxpresto(8X)NAMEdxpresto - Graphically displays Prestoserve state and statistics.
SYNOPSIS
/usr/bin/X11/dxpresto [-option]...
OPTIONS
Specifies the color of the window's border (color displays only). The
default is black. Specifies the color of the window's background
(color displays only). The default is white. Specifies the display
screen on which dxpresto displays its window. If the display option is
not specified, dxpresto uses the display screen specified by your DIS‐
PLAY environment variable. The display variable has the format host‐
name:number. Using two colons (::) instead of one (:) indicates that
DECnet is to be used for transport. The default is :0. For more
information, see X(1X). This option is the same as the -d option.
Specifies the color of the text (color displays only). The default is
black. Specifies the width, length, and location of the dxpresto win‐
dow. If the geometry option is not specified, dxpresto uses default
values. The geometry option has the format =[width][xlength][x][y]. For
more information about the screen coordinate system, see X(1X).
DESCRIPTION
The dxpresto command is an X Window System application that graphically
displays a machine's Prestoserve state and statistics. The dxpresto
command uses a Remote Procedure Call (RPC) protocol to communicate with
the machine being monitored. You use the dxpresto command to provide
general information about Prestoserve and to help manage Prestoserve.
Also, you can use the command to demonstrate the efficacy of the
Prestoserve software.
The machine that you want to monitor must be running the prestoctl_svc
daemon and the portmap daemon.
Because dxpresto is an X Window System application, your DISPLAY envi‐
ronmental variable must be set to a machine that is an X Server. For
more information, see X(1X).
dxpresto Window
The dxpresto window contains the following information: Displays the
name of the machine that is running dxpresto. Show the Prestoserve
state, either Enabled (UP), Disabled (DOWN), or Error (ERROR). Dis‐
plays the interval of time in seconds between Prestoserve queries and
allows you to change that interval. When you invoke the dxpresto com‐
mand, the default sample interval is 5; therefore Prestoserve informa‐
tion is gathered every five seconds. For example, if you want
Prestoserve queried more often, move the slider to the left and click
on MB1 until 2 appears; Prestoserve is then queried every two seconds.
Shows the time since Prestoserve was last enabled. The time is dis‐
played in hours, minutes, and seconds. The total number of seconds is
also shown. Show the state of the Prestoserve backup battery system.
An intact battery icon with the word ok indicates that the battery has
sufficient power. An intact battery icon with the word low indicates
that the battery's power is low. A broken battery icon indicates that
the battery is disabled. Prestoserve goes into the ERROR state when
the backup battery power falls below a minimum amount. Contact the
server administrator or the server hardware Field Service representa‐
tive if a battery is low or disabled. Displays the number of Kbytes of
nonvolatile memory that the Prestoserve cache is utilizing. Note that
Prestoserve can utilize less than the default maximum size of its
Prestoserve cache if you changed the cache size with the presto -s com‐
mand. Allows you to display or to not display graphs that demonstrate
how the Prestoserve cache is being utilized. Allows you to display or
to not display the Prestoserve cache statistics table. Allows you to
exit from dxpresto. Displays error messages and informational messages
for both Prestoserve and the dxpresto command.
Some error messages, such as those indicating RPC communication
failure, are displayed on the terminal from which you invoked
the dxpresto command.
Cache Utilization Graphs
If you enable the Display Cache Utilization graphs, the following is
displayed: Shows how the Prestoserve cache operations are distributed
among the four Prestoserve buffer states: dirty, clean, inval, and
active. The vertical axis shows the maximum number of objects or disk
blocks that the entire Prestoserve cache can contain. The sum of the
four bars is the total number of buffers used in the Prestoserve cache.
Note that the size of the Prestoserve cache can be changed by using the
presto -s command. Shows a recent history of the average number of
writes per second over the time intervals that are determined by the
sample interval.
Each point in the horizontal axis represents a sample time
interval as determined by the sample interval; the maximum num‐
ber of samples that can be shown is 210. When you reach the
maximum number of samples, the graph shifts to the left so you
can see at least the last 105 samples, which is half the maximum
number of samples. If you choose 5 as the sample interval,
Prestoserve is queried every five seconds; therefore it takes
1050 (5 x 210) seconds to obtain the maximum of 210 samples.
The vertical axis shows the average number of writes performed
per second within the sample time interval as determined by the
sample interval.
For example, if you choose 2 as the sample interval, Prestoserve
is queried every two seconds, and each point in the graph shows
the average number of writes performed within the interval of
two seconds. If the graph shows that an average of 5 writes per
second were performed within two seconds, Prestoserve actually
performed 10 writes within those two seconds. The calculation
is:
L 5 writes ---------- x 2 sec = 10 writes
sec Shows a recent history of the average number of
Prestoserve cache hits per second over the time intervals that
are determined by the sample interval. The Prestoserve cache
hits represent the total number of clean and dirty read and
write hits (blocks that match blocks already in the cache).
Each point in the horizontal axis represents a sample time
interval as determined by the sample interval; the maximum num‐
ber of samples that can be shown is 210. When you reach the max‐
imum number of samples, the graph shifts to the left so you can
see at least the last 105 samples, which is half the maximum
number of samples. If you choose 2 as the sample interval,
Prestoserve is queried every two seconds; therefore it takes 420
(2 x 210) seconds to obtain the maximum of 210 samples.
The vertical axis shows the average number of hits performed per
second within the sample time interval as determined by the sam‐
ple interval.
For example, if you choose 10 as the sample interval,
Prestoserve is queried every 10 seconds, and each point in the
graph shows the average number of hits performed within the
interval of 10 seconds. If the graph shows that an average of 2
hits per second were performed within 10 seconds, Prestoserve
actually performed 20 writes within those 10 seconds. The calcu‐
lation is:
2 hits ---------- x 10 sec = 20 hits
sec
Cache Statistics Table
If you enable the Display Cache Statistics table, the following is dis‐
played: Allows you to display Prestoserve statistics since Prestoserve
was last enabled. This is useful when you want to determine how
Prestoserve performs over a long period of time. Allows you to display
the Prestoserve statistics for each sample time interval as determined
by the Sample Interval slider. If no Prestoserve activity occurs dur‐
ing the time interval, the numbers in the statistics table are zero.
For example, if the Sample Interval slider is set to 5 and the Since
last Sample button is enabled, the statistics table shows the
Prestoserve statistics for each interval of five seconds. Allows you
to display Prestoserve statistics since you clicked on the Zero button.
This button allows you to determine how Prestoserve performs over a
specific period of time that you can set by using the Zero button.
Allows you to set a time reference for the Prestoserve statistics ta‐
ble. If you click on the Zero button and, at a later time, click on the
Since last Zero button, the table displays the Prestoserve statistics
since you clicked on the Zero button. Shows information similar to the
information that is displayed when you use the presto -p command. For
each Prestoserve cache read or write operation, Prestoserve increments
an appropriate counter. The table shows: The Write Cache Efficiency,
which is the ratio of write dirty hits to the number of writes copied
into the Prestoserve cache The Count, which is the sum of the clean
hits, dirty hits, and allocations, and passes The Hit rate percentage,
which is the ratio of clean hits and dirty hits to the total count The
Clean hits counter, which is the number of hits on the clean buffers
The Dirty hits counter, which is the number of hits on the dirty buf‐
fers (each dirty hit represents a physical disk write that was avoided
entirely) The Allocations counter, which is the number of new buffers
that had to be allocated for disk block images The passes counter,
which is the number of I/O operations that Prestoserve passed directly
to the actual device driver
X DEFAULTS
The dxpresto application uses the values in the file when you logged in
and uses the appropriate resource specification to customize the
appearance or characteristics of its displayed dxpresto window. The
format for a resource specification in the file is: [name*]resource:
value
Specifies the application name or the name string that restricts the
resource assignment to that application or to a component of an appli‐
cation. If this argument is not specified, the resource assignment is
globally available to all X applications. Specifies the resource.
Specifies the value that is to be assigned to the resource.
For more information, see X(1X).
Because each toolkit-based application can consist of a combination of
widgets (for example, push buttons and a scroll bar), you can form the
name string by adding widget class and name identifiers to the string.
For further information about adding class and name identifiers, see
X(1X).
For dxpresto, the available name identifiers are: The dialog box con‐
taining all of the graphs The graph displaying dirty buffers The graph
displaying clean buffers The graph displaying inval buffers The graph
displaying active buffers The graph displaying cache write history The
graph displaying cache hit history
EXAMPLES
The following is an example of the suggested resource values:
DXpresto*background: darkslategray DXpresto*fore‐
ground: wheat1 DXpresto*borderColor:
gold3 DXpresto*graph_parent*borderColor: firebrick
DXpresto*dirty_graph*highlight: gold3
DXpresto*dirty_graph*background: black
DXpresto*clean_graph*highlight: gold3
DXpresto*clean_graph*background: black
DXpresto*inval_graph*highlight: gold3
DXpresto*inval_graph*background: black
DXpresto*active_graph*highlight: gold3
DXpresto*active_graph*background: black
DXpresto*write_graph*highlight: gold3
DXpresto*write_graph*background: black DXpresto*hit_graph*high‐
light: gold3 DXpresto*hit_graph*background: black
DXpresto*topShadowColor: gold2 DXpresto*bottomShadow‐
Color: gold4 DXpresto*armColor: gold3
DXpresto*selectColor: gold3
DXpresto*presto_on.selectColor: green
DXpresto*presto_off.selectColor: yellow
DXpresto*presto_error.selectColor: red
FILESSEE ALSOX(1X), presto(7), portmap(8), presto(8), prestoctl_svc(8)
Guide to Prestoserve
dxpresto(8X)