The Utilization Graph provides a graphical representation of the data in MobiLink Monitor.
This tab has the following components:
Utilization statistics list Select and clear the properties listed to specify which properties appear in the utilization graph.
Show Select this option to show the property in the utilization graph. Properties without a checkmark do not appear.
Property Shows the available properties that you can choose to appear in the utilization graph. Only properties with a checkmark appear in the graph.
The list of properties comes from the MobiLink server or the .mlm file, and is saved in .mlMonitorSettings12. If you delete .mlMonitorSettings12, the properties are listed as numbers.
The possible properties are:
Busy DB workers This value indicates how many database worker threads are doing something in the consolidated database. There is no distinction between inserts, updates, deletes, or selects. When this value is zero, no database worker threads are using the consolidated database. See -w mlsrv12 option and -wu mlsrv12 option.
Command processor work queue This represents the amount of pending requests for the MobiLink server; both to interpret internal MobiLink protocol commands and to apply these commands to the consolidated database. Request types include synchronization requests, MobiLink Listener requests, MobiLink File Transfer utility (mlfiletransfer) requests, and so on.
Dynamic Cache work Queue This queue represents the length of time it takes to perform dynamic cache sizing. This line is hidden by default.
Heartbeat work queue This queue represents the layer in the MobiLink server that is responsible for sending pulsed events within the server. This layer is responsible, for example, for triggering the once-per-second pulses of samples to the connected MobiLink Monitors.
It is highly unlikely that this queue gets backed up so it is not visible by default.
Notifier work queue This represents the size of the Notifier work queue. The queue size increases if the consolidated database is slow to respond with the results of the Notifier's queries.
The Notifier's queries for Remote Tasks are very simple, but may return many rows in large deployments. The queue size is proportional to the length of time it takes the Notifier to retrieve the Remote Task notifications.
OE work Queue This represents the size of the Outbound Enabler (OE) queue. The queue size is proportional to the network I/O activity between the MobiLink server being monitored and the Relay Server(s).
Stream work queue This queue represents pending work for the high-level network layer in the MobiLink server. This layer is responsible for higher-level network protocol work such as HTTP, encryption, and compression. This queue grows when a lot of reads come in from the TCP/IP layer and when a lot of write requests come in from the Command processor layer.
TCP/IP work queue This queue represents pending for the low-level network layer in the MobiLink server. This layer is responsible for both reading and writing packets from and to the network. The queue shows the number of requests to read incoming network data and the number of requests from the stream layer to write to the network.
This queue gets longer if there is a backlog of either network reads or writes—sometimes both, but usually one or the other. Reads can get backed up if the MobiLink server is using a lot of RAM and memory pages are being swapped in and out a lot. Consider getting more RAM in this case. Writes can get backed up if the network connection between the clients and server is slow. If this queue is the only queue that is backed up, look at the CPU usage. If CPU usage is high, there may be read/memory problems. If CPU usage is low, you may have slow writes due to network slowness.
Color For each property, click Color and select a color from the dropdown list that is used to represent the selected property in the utilization graph.
Scale For each property, a scale factor is used so that the property value can be displayed between 0 and 100 on the Utilization Graph.
The default scale factor is 5, meaning that values are expected to be in a range of 0 to 20, scaled (by 5) to the range 0 to 100. If a value becomes greater than 20, the scale is automatically adjusted such that the largest value is displayed at 100 in the graph.
To determine the maximum value in the display when the scale has been automatically adjusted, divide the scale into 100. For example, if the TCP/IP work queue scale is 2.381, then the maximum value is ( 100 / 2.381 ) = 42. The actual maximum isn't usually important. What is important is that values towards the top of the graph are approaching the largest currently-known value for the given property—in other words, the peak load for that property as observed in the current monitoring session.
When the graphs are consistently towards the top of the display and you notice that synchronization throughput is down, you may have a performance problem that needs investigation. Similarly, if one or more values creeps upward over time without diminishing, then there is likely a performance problem. Note that the graphs may often be towards the top of the display with MobiLink server is busy and performing well.
Selection border Select a color from the dropdown list for the border of the utilization graph. By default, the border is Black.
Grid lines Select a color from the dropdown list for the grid lines. By default, the grid lines are Light Gray.
Graph background Select a color from the dropdown list for the graph background. By default, the graph background is White.
Use antialiasing to smooth graph Antialiasing is a technique used to make graphics look smoother. Selecting this option makes the graph look better, but it may be slower to draw.
See also |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |