Lotus Domino platform statistics on Linux

Document options Document options requiring JavaScript are not displayed Rate this page Help us improve this content

Level: Intermediate

Joe Malek, Software Engineer, IBM

02 Aug 2004

The platform statistics feature has long been one of the most powerful system analysis tools in Lotus Domino. In Domino 6.5, this feature has been extended to the Linux platform. This article explains how you can use platform statistics for Lotus Domino on Linux to help make your job as administrator easier.

Monitoring a Domino server on Linux can be quite a task because you need to gather both Domino statistics and operating system statistics. Fortunately, you can use the Tivoli Analyzer for Domino, Domino Administrator client, or Domino console to utilize the platform statistics feature in Lotus Domino to view a Domino on Linux system.

This article introduces you to platform statistics for Linux. We begin with a brief overview of the platform statistics feature. Then we compare using native operating system tools to collect data versus using platform statistics. This shows you the effort you would need to devote to manually monitoring the resources of a UNIX system and how Domino platform statistics simplifies this process (allowing you to focus on analyzing the data rather than collecting and processing it). Next we discuss the types of data platform statistics can provide for Linux and show a sample report.

This article assumes that you're an experienced Domino administrator and are familiar with Linux.

A quick overview of platform statistics

The platform statistics feature was introduced in Lotus Domino 5.0.2 for Windows NT and Solaris Sparc. Lotus Domino 6 added platform statistics support to Windows 2000 and AIX. Platform statistics for Linux on Intel and for Linux on zSeries were introduced in Lotus Domino 6.5, offering a limited set of statistics. (In this article, all references to Linux will include both Linux on Intel and Linux on zSeries unless otherwise noted.) Current plans for Lotus Domino 7.0 call for platform statistics support for Windows 2003 (.Net) and extend platform statistics for Domino on Linux to include process-level statistics.

Platform statistics provide you with operating system and limited Domino server partition statistics (process/task statistics for that particular partition only). If you're an experienced Domino administrator, you are probably already familiar with platform statistics and have developed practices, methodologies, or even applications that build upon this information. Platform statistics on Linux should fit nicely into these practices, as many of these statistics can be analyzed through your existing methods.

Before platform statistics, collecting data about the behavior of a system was complicated and time-consuming. Administrators had to perform numerous steps and issue many commands to organize and collect this data. For instance, commands such as iostat (which reports disk and cpu statistics), vmstat (memory and cpu statistics), netstat (network statistics), and top or ps (process statistics) all had to be enabled to collect data over long periods of time. This information then needed to be collected in a file and processed further to be understandable and useful. After this was collected, the administrator needed to examine many lines of data for each output file to determine what was happening. This required a significant amount of time that could be better spent on other tasks (such as fine-tuning system performance). The next section of this article compares the simplicity of automatically collecting platform statistics data with the many steps involved in manually collecting data and converting it to a readable and meaningful format.

Platform statistics are integrated with Domino Stats and Events. Therefore, they can be collected via the Domino Monitoring Configuration database (events4.nsf) and displayed within the Monitoring Results database (statrep.nsf). Within the Domino Monitoring Configuration database, you can set thresholds and alarms for server resource usages within Lotus Domino. Within this database, you can examine the latest definitions and data about supported platforms by viewing the Advanced folder, the platform statistics folder, and finally the Domino 6 view from a Domino 7 server. (No changes were made to statistic names between release 6 and 7, so they share the same view.) For Domino 5 statistics, see the Domino 5 view under the same location.

The collect task must be running on the server, otherwise platform statistics will not be collected in the Monitoring Results database. If the collect task is not enabled, platform statistics can still be viewed on the server console (more on this later). The collected data can be found in the Monitoring Results database under the Statistics Reports folder and the Platform view within it.

Platform statistics results are available via the server console, the Domino Administrator client, and the Web Administrator client. When you issue a Show Stat Platform command on the server console in Lotus Domino 7 on Linux (or view the collected statistics for a particular interval in the Monitoring Configuration database), over 100 statistics are shown. The naming convention for the statistics that are reported is the same across platforms, which makes it easier for a single administrator to support multiple server platforms. Both Domino statistics and operating system statistics can be collected together in real-time and for historical trend analysis. Some of the platform statistics numbers are also used for various probes within the Domino Domain Manager (Domino 7 server only) and Tivoli Analyzer for Domino features.

Platform statistics versus Linux performance monitoring tools

To appreciate the power of the Domino platform statistics feature, compare it to the work you would need to perform to obtain these results through the operating system itself.

Memory and CPU (vmstat) statistics
For example, to view memory and CPU data using Linux system tools, run the Linux performance tool vmstat by typing the following at the command line of a Linux window:

This starts the collection of memory and CPU statistics and displays output in an interval of every 60 seconds. (An interval less than 60 seconds is not recommended because the accuracy of the data decreases.) The data is saved in a file called CPUoutput.txt. The vmstat tool runs for the length of time you want to sample data from the server. You can view this file to help determine what happened during the run, for example:

	procs			memory			  swap
r	b	w	swpd	free	buff	cache	si	so
1	0	0	225852	131604	130404	1364204	0	0
0	0	0	225852	131604	130404	1364204	0	0
0	0	0	225852	131604	130404	1364204	0	0
0	0	0	225852	131604	130404	1364204	0	0
3	0	0	225852	131292	130404	1364204	0	0
0	0	0	225852	131292	130408	1364204	0	0

	io		system		cpu

	bi	bo	in	cs	us	sy	id
	0	0	0	0	2	0	100
	0	0	0	58	2	0	100
	0	18	0	70	2	0	100
	0	0	0	67	2	0	100
	0	8	0	225	2	1	97
	0	96	0	179	2	1	98

This data is raw in that you need to perform some calculations to convert it to a meaningful format. For instance:

• Column 4 (labelled swpd) shows the swap used, but you need total swap size to get the percentage utilized and available swap remaining. You can find the total swap size in /pro/meminfo. You can then subtract the swpd value from the total to find the free swap.
• Columns 8 and 9 (labelled si and so) represent the pages (in KB) swapped in and out of memory, respectively. Add these per interval to get the pages swapped per second.
• Columns 13 through 15 display the context switches, the user CPU utilization, and the kernel CPU utilization for that interval. Divide the context switches by 60 to calculate the rate and add the user and kernel CPU to get the total CPU utilization for the interval.

User and system CPU (top) statistics
The top command creates an output file that stores user and system CPU resources for each processor. To issue the top command, type /usr/bin/top in the Linux command line and then use the interactive "s" command within top to set the interval to at least 60 seconds. This produces data similar to the following:

6:55am: up 36 days, 26 min, 1 user, load average: 0.00, 0.00, 0.00
53 processes: 52 sleeping, 1 running, 0 zombie, 0 stopped
CPU0 states: 0.0% user, 0.0% system, 0.0% nice, 100.0% idle
CPU1 states: 0.0% user, 0.1% system, 0.0% nice, 99.0% idle
Mem: 1032232K av, 1016716K used, 15516K free, 0K shrd, 135144K buff
Swap: 2097136K av, 0K used, 2097136K free, 729980K cached

PID 	USER	PRI	NI	SIZE	RSS	SHARE	STAT 	%CPU
14578 	user    15  	0	952	952	756 	R	0.9 
1 	root  	15   	0 	236	236	204 	S	0.0
4 	root 	15   	0	0	0	0 	SW	0.0
7 	root	15   	0	0	0	0 	SW	0.0
8 	root	25   	0	0	0	0 	SW	0.0
9 	root	15   	0	0	0	0 	SW	0.0
371 	root	15   	0 	468	468	400 	S	0.0
390 	root	15   	0	696	696	560 	S	0.0
394 	root	15   	0	1504	1504	428 	S	0.0
469 	bin	15   	0	480	480	396 	S	0.0

	%MEM	TIME	COMMAND
	0.0	0:00	top
	0.0	0:04	init
	0.0	0:00	keventd
	0.0	0:18	kswapd
	0.0	0:00	bdflush
	0.0	0:11	kupdated
	0.0	0:00	dhcpcd
	0.0	0:00	syslogd
	0.1	0:00	klogd
	0.0	0:02	portmap

Adding up each number for the total number of processors produces the total CPU for that interval. To obtain the swap utilization, you must calculate total swap. Subtracting the used swap from the total results in the free swap.

Disk (iostat) statistics
To gather disk statistics, open the Linux command line and type:

This enables the collection of disk data for each 60 second interval, for example:

Linux 2.4.21-138-smp (mymachine)  

avg-cpu:	%user	%nice	%sys	%idle
		2.59	0.04	0.10	97.27

Device:		rrqm/s	wrqm/s	r/s	w/s	rsec/s	wsec/s	rkB/s
/dev/sda	0.92	1.93	0.34	0.19	10.06	17.04	5.03
/dev/sda1	0.04	0.04	0.01	0.00	0.34	0.33	0.17
/dev/sda2	0.88	1.89	0.33	0.19	9.72	16.70	4.86
/dev/sdb	0.11	0.87	0.02	0.15	1.08	8.18	0.54
/dev/sdb1	0.11	0.87	0.02	0.15	1.08	8.18	0.54

  wkB/s	avgrq-sz	avgqu-sz	await	svctm	%util
  8.52	50.96		0.60		1799.74	663.85	3.53
  0.17	113.85		0.00		363.57	123.96	0.01
  8.35	50.25		0.96		1815.87	55.04	0.29
  4.09	53.59		0.03		403.27	217.36	0.38
  4.09	53.60		0.11		403.30	264.38	0.46


avg-cpu:	%user	%nice	%sys	%idle
		2.25	0.00	0.00	97.75

Device:		rrqm/s	wrqm/s	r/s	w/s	rsec/s	wsec/s	rkB/s
/dev/sda	0.00	0.00	0.00	0.00	0.00	0.00	0.00
/dev/sda1	0.00	0.00	0.00	0.00	0.00	0.00	0.00
/dev/sda2	0.00	0.00	0.00	0.00	0.00	0.00	0.00
/dev/sdb	0.00	0.00	0.00	0.00	0.00	0.00	0.00
/dev/sdb1	0.00	0.00	0.00	0.00	0.00	0.00	0.00

  wkB/s	avgrq-sz	avgqu-sz	await	svctm	%util
  0.00	0.00		2.48		0.00	0.00	100.00
  0.00	0.00		0.00		0.00	0.00	0.00
  0.00	0.00		0.00		0.00	0.00	0.00
  0.00	0.00		2.48		0.00	0.00	100.00
  0.00	0.00		10.00		0.00	0.00	100.00

The first sample of data from iostat is a summary covering the running time of the operating system; ignore this data. Then for each device of interest:

• Column 11 (avgqu-sz) is the average queue length of that particular disk.
• Column 13 (svctm) is the service time of the disk over the interval.
• Column 14 (%util) is the percentage of time the disk was busy.

Network (netstat) statistics
To collect network statistics, issue the following command on the Linux command line:

/usr/bin/netstat -c -e -I 'devicename' > networkstats.txt

where 'devicename' is the name of the network card you want to sample. This enables the collection of network statistics for each second. (This doesn't have the capability to change the interval, so to obtain metrics on a per-minute basis examine every 60th sample.) For each device of interest, you are shown the following data:

Kernel Interface table
eth0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:x.x.x.x  Bcast:x.x.x.x  Mask:x.x.x.x
          inet6 addr: x::x:x:x:x Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4563287 errors:0 dropped:0 overruns:0 frame:0
          TX packets:744150 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:4023960946 (3837.5 Mb)  TX bytes:126653260 (120.7 Mb)
          Interrupt:10 Base address:0x3040 Memory:febff000-febff038
          
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:882 errors:0 dropped:0 overruns:0 frame:0
          TX packets:882 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:58924 (57.5 Kb)  TX bytes:58924 (57.5 Kb)

With netstat, some of the values are commutative. This means you must take values at one sample and then subtract them from the previous sample to get the actual value.

Process (ps) statistics
For process statistics, you must issue the command ps -ao comm,pid,pcpu on the Linux command line for each interval. Then scroll down to view the name/PID/%CPU combinations to see what the Domino processes are doing. (If multiple partitions are running, it's very difficult to determine which processes belong to which partition using this method.)

COMMAND	PID	%CPU
sh	1138	0.1
server	1190	4.8
server	1191	0.0
server	1192	0.0
server	1199	0.0
server	1200	3.9
event	1380	7.7
event	1406	0.0
event	1407	0.0
server	1411	3.1
event	1521	0.0
server	1538	0.0
server	1539	0.0
server	1540	0.0
update	1542	0.2
replica	1543	0.3
router	1544	2.4
amgr	1545	2.2
adminp	1546	0.9
calconn	1547	0.1
sched	1548	1.3
http	1549	20.0
imap	1550	1.7
server	1559	0.0
server	1561	0.0
server	1562	0.0
server	1563	0.0

Typically, this report includes hundreds of threads/processes, each of which you would have to examine to identify the correct PIDs for the Domino server tasks of interest.

Fortunately, the Domino platform statistics feature allows you to view this data with far less time and effort. For Domino partitions, the process statistics listed are for that partition only. (There will always be some discrepancy between platform statistics and data obtained by native operating system monitoring tools such as iostat or perfmon for Windows.)

Platform statistics on Linux

Platform statistics bring all the raw system level data to you and organizes it into groupings (or contexts) for each type of operating system resource being monitored, using statistic names and formats consistent across the Domino server platforms. This groups data into an easy to read format, providing data such as per second rates, percentages, and total counts. All the data is sampled over a specified interval from as short as one minute up to one day.

To view raw platform statistics, use the Show Stat Platform command. With this command, you can display all platform statistics or a selected subset of them. You can enter Show Stat Platform at the server console to display local server platform statistics. You can also type this command at the remote server console to display remote server platform statistics.

The Show Stat Platform command displays the following operating system level information:

As mentioned earlier, platform statistics can also be viewed through the Domino Administrator client, Domino Domain Manager probes, and Server Health Monitoring. For more information on how to view platform statistics, see the Domino Administrator on-line help.

Back to top

Example console output

This section shows examples of platform statistics generated by the Show Stat Platform command on the server console for both Linux on Intel and Linux for zSeries. By examining the data, you can see that each resource (disk, network interface card, and process) is broken down to display what is happening with individual resources. Each resource is shown with a set of statistics related to that resource. Using these statistics, you can determine the behavior of the system as a whole and see the Domino process statistics relative to a particular partition. This can provide a quick glance at the system or a way to investigate situations that may arise. For example, you can drill down to the individual resource level to see which one could be a bottleneck (disk, process, network, and so on).

First let's look at statistics for Linux for Intel:

Platform.LogicalDisk.1.AssignedName=sda
Platform.LogicalDisk.1.AvgQueLen.Avg=1
Platform.LogicalDisk.1.AvgQueLen.Peak=1
Platform.LogicalDisk.1.AvgQueLen=0
Platform.LogicalDisk.1.PctUtil.Avg=1
Platform.LogicalDisk.1.PctUtil.Peak=3
Platform.LogicalDisk.1.PctUtil=0
Platform.LogicalDisk.1.ServiceTimeinmsecs.Avg=5
Platform.LogicalDisk.1.ServiceTimeinmsecs.Peak=25
Platform.LogicalDisk.1.ServiceTimeinmsecs=70
Platform.LogicalDisk.TotalNumofDisks=1
Platform.Memory.PagesPerSec=0
Platform.Memory.RAM.AvailMBytes.Avg=134.94
Platform.Memory.RAM.AvailMBytes.Min=106.02
Platform.Memory.RAM.AvailMBytes.Peak=185.3
Platform.Memory.RAM.AvailMBytes=130.05
Platform.Memory.RAM.PctUtil=87.1
Platform.Memory.RAM.TotalMBytes=1,008.04
Platform.Network.1.AdapterName=eth0
Platform.Network.1.BytesRecvdPerSec=3,370
Platform.Network.1.BytesSentPerSec=71.33
Platform.Network.1.NetworkBytesPerSec=3,441.33
Platform.Network.1.PctCollisionRate=0
Platform.Network.Total.BytesRecvdPerSec=3,370
Platform.Network.Total.BytesSentPerSec=71.33
Platform.Network.Total.NetworkBytesPerSec=3,441.33
Platform.Network.Total.PctCollisionRate=0
Platform.Network.TotalNumofAdapters=1
Platform.PagingFile.Free.SizeMBytes=2,046.05
Platform.PagingFile.Total.PctUtil.Avg=0.74
Platform.PagingFile.Total.PctUtil.Peak=2.05
Platform.PagingFile.Total.PctUtil=0.09
Platform.PagingFile.Total.SizeMBytes=2,047.98
Platform.Process.ActiveDomino.TotalCpuUtil=0.3
Platform.Process.ActiveNumOfDominoProc=15
Platform.Process.adminp.1.PctCpuUtil=0.1
Platform.Process.adminp.1.ProcessID=12233
Platform.Process.amgr.1.PctCpuUtil=0
Platform.Process.amgr.1.ProcessID=12232
Platform.Process.amgr.2.PctCpuUtil=0
Platform.Process.amgr.2.ProcessID=12379
Platform.Process.calconn.1.PctCpuUtil=0
Platform.Process.calconn.1.ProcessID=12234
Platform.Process.event.1.PctCpuUtil=0
Platform.Process.event.1.ProcessID=11970
Platform.Process.imap.1.PctCpuUtil=0
Platform.Process.imap.1.ProcessID=12259
Platform.Process.ldap.1.PctCpuUtil=0.1
Platform.Process.ldap.1.ProcessID=12260
Platform.Process.pop3.1.PctCpuUtil=0
Platform.Process.pop3.1.ProcessID=12276
Platform.Process.replica.1.PctCpuUtil=0.1
Platform.Process.replica.1.ProcessID=12228
Platform.Process.router.1.PctCpuUtil=0
Platform.Process.router.1.ProcessID=12229
Platform.Process.sched.1.PctCpuUtil=0
Platform.Process.sched.1.ProcessID=12256
Platform.Process.server.1.PctCpuUtil=0
Platform.Process.server.1.ProcessID=11828
Platform.Process.smtp.1.PctCpuUtil=0
Platform.Process.smtp.1.ProcessID=12277
Platform.Process.update.1.PctCpuUtil=0
Platform.Process.update.1.ProcessID=12227
Platform.System.ContextSwitchesPerSec.Avg=2,075.42
Platform.System.ContextSwitchesPerSec.Min=1,933.95
Platform.System.ContextSwitchesPerSec.Peak=2,413.15
Platform.System.ContextSwitchesPerSec=1,950.58
Platform.System.PctCombinedCpuUtil.Avg=6.68
Platform.System.PctCombinedCpuUtil.Peak=18.24
Platform.System.PctCombinedCpuUtil=6.22
Platform.System.PctTotalPrivilegedCpuUtil.Avg=0.31
Platform.System.PctTotalPrivilegedCpuUtil.Peak=3.71
Platform.System.PctTotalPrivilegedCpuUtil=0.3
Platform.System.PctTotalUserCpuUtil.Avg=6.37
Platform.System.PctTotalUserCpuUtil.Peak=14.52
Platform.System.PctTotalUserCpuUtil=5.92
Platform.Time.LastSample=05/18/2004 06:06:54 EDT
Platform.Time.SampleRateInMins=1

Here's an example of Show Stat Platform statistics for Linux for zSeries:

Platform.LogicalDisk.1.AssignedName = dasda
Platform.LogicalDisk.1.AvgQueLen = 0
Platform.LogicalDisk.1.AvgQueLen.Avg = 0
Platform.LogicalDisk.1.AvgQueLen.Peak = 0
Platform.LogicalDisk.1.PctUtil = 0
Platform.LogicalDisk.1.PctUtil.Avg = 0
Platform.LogicalDisk.1.PctUtil.Peak = 0
Platform.LogicalDisk.1.ServiceTimeinmsecs = 0
Platform.LogicalDisk.1.ServiceTimeinmsecs.Avg = 0
Platform.LogicalDisk.1.ServiceTimeinmsecs.Peak = 0
Platform.LogicalDisk.2.AssignedName = dasdb
Platform.LogicalDisk.2.AvgQueLen = 0
Platform.LogicalDisk.2.AvgQueLen.Avg = 0
Platform.LogicalDisk.2.AvgQueLen.Peak = 0
Platform.LogicalDisk.2.PctUtil = 0
Platform.LogicalDisk.2.PctUtil.Avg = 0
Platform.LogicalDisk.2.PctUtil.Peak = 0
Platform.LogicalDisk.2.ServiceTimeinmsecs = 0
Platform.LogicalDisk.2.ServiceTimeinmsecs.Avg = 0
Platform.LogicalDisk.2.ServiceTimeinmsecs.Peak = 0
Platform.LogicalDisk.TotalNumofDisks = 2
Platform.Memory.PagesPerSec = 0
Platform.Memory.RAM.AvailMBytes = 6.09
Platform.Memory.RAM.AvailMBytes.Avg = 5.82
Platform.Memory.RAM.AvailMBytes.Min = 5.54
Platform.Memory.RAM.AvailMBytes.Peak = 6.09
Platform.Memory.RAM.PctUtil = 99.68
Platform.Memory.RAM.TotalMBytes = 1,890.36
Platform.Network.1.AdapterName = eth0
Platform.Network.1.BytesRecvdPerSec = 5.15
Platform.Network.1.BytesSentPerSec = 3.5
Platform.Network.1.NetworkBytesPerSec = 8.65
Platform.Network.1.PctCollisionRate = 0
Platform.Network.TotalNumofAdapters = 1
Platform.Network.Total.BytesRecvdPerSec = 5.15
Platform.Network.Total.BytesSentPerSec = 3.5
Platform.Network.Total.NetworkBytesPerSec = 8.65
Platform.Network.Total.PctCollisionRate = 0
Platform.PagingFile.Free.SizeMBytes = 1,827.43
Platform.PagingFile.Total.PctUtil = 10.77
Platform.PagingFile.Total.PctUtil.Avg = 10.77
Platform.PagingFile.Total.PctUtil.Peak = 10.77
Platform.PagingFile.Total.SizeMBytes = 2,047.98
Platform.Process.ActiveDomino.TotalCpuUtil = 0
Platform.Process.ActiveNumOfDominoProc = 15
Platform.Process.adminp.1.PctCpuUtil = 0
Platform.Process.adminp.1.ProcessID = 18206
Platform.Process.amgr.1.PctCpuUtil = 0
Platform.Process.amgr.1.ProcessID = 18205
Platform.Process.amgr.2.PctCpuUtil = 0
Platform.Process.amgr.2.ProcessID = 18384
Platform.Process.calconn.1.PctCpuUtil = 0
Platform.Process.calconn.1.ProcessID = 18207
Platform.Process.event.1.PctCpuUtil = 0
Platform.Process.event.1.ProcessID = 18166
Platform.Process.http.1.PctCpuUtil = 0
Platform.Process.http.1.ProcessID = 18253
Platform.Process.imap.1.PctCpuUtil = 0
Platform.Process.imap.1.ProcessID = 18254
Platform.Process.ldap.1.PctCpuUtil = 0
Platform.Process.ldap.1.ProcessID = 18255
Platform.Process.pop3.1.PctCpuUtil = 0
Platform.Process.pop3.1.ProcessID = 18257
Platform.Process.replica.1.PctCpuUtil = 0
Platform.Process.replica.1.ProcessID = 18202
Platform.Process.router.1.PctCpuUtil = 0
Platform.Process.router.1.ProcessID = 18204
Platform.Process.sched.1.PctCpuUtil = 0
Platform.Process.sched.1.ProcessID = 18210
Platform.Process.server.1.PctCpuUtil = 0
Platform.Process.server.1.ProcessID = 17867
Platform.Process.smtp.1.PctCpuUtil = 0
Platform.Process.smtp.1.ProcessID = 18259
Platform.Process.update.1.PctCpuUtil = 0
Platform.Process.update.1.ProcessID = 18201
Platform.System.ContextSwitchesPerSec = 2,629.17
Platform.System.ContextSwitchesPerSec.Avg = 2,647.09
Platform.System.ContextSwitchesPerSec.Min = 2,629.17
Platform.System.ContextSwitchesPerSec.Peak = 2,665.02
Platform.System.PctCombinedCpuUtil = 2.87
Platform.System.PctCombinedCpuUtil.Avg = 7.55
Platform.System.PctCombinedCpuUtil.Peak = 12.23
Platform.System.PctTotalPrivilegedCpuUtil = 0.29
Platform.System.PctTotalPrivilegedCpuUtil.Avg = 1.77
Platform.System.PctTotalPrivilegedCpuUtil.Peak = 3.26
Platform.System.PctTotalUserCpuUtil = 2.58
Platform.System.PctTotalUserCpuUtil.Avg = 5.78
Platform.System.PctTotalUserCpuUtil.Peak = 8.97
Platform.Time.LastSample = 05/18/2004 10:27:57 EDT
Platform.Time.SampleRateInMins = 1

Back to top

Conclusion

Platform statistics provide a one stop location for system performance information. Whether you're using the Domino Administrator client to view historical trend or real-time statistics, the Domino Domain Manager probes (agents, system), Server Health Monitoring, or just viewing raw statistics on the server console or in the Monitoring Results database, you can see the value in platform statistics. We encourage all our users to collect data from their environments, whether for preventive monitoring, for measuring a baseline configuration, for finding server system bottlenecks, or for debugging an environment. Platform statistics can help make any and all of these jobs easier. As always, we appreciate hearing from you (especially any feedback or results) based on your experience.

Resources

• For more information on how to view platform statistics, see the Domino Administrator on-line help.
  
  
• The developerWorks: Lotus article, "New features in Notes/Domino 6.5," lists all the new administration features (including platform statistics for Linux) introduced in Lotus Domino 6.5.
  
  
• Participate in developerWorks blogs and get involved in the developerWorks community.

About the author

		Joe Malek is a developer for the IBM Domino Performance team. His current focus involves developing performance tools for the Domino Performance team working on various platforms such as Microsoft .Net, Linux, IBM AIX, and Sun Solaris. Joe joined Iris Associates/Lotus in October 2000.

Rate this page

Please take a moment to complete this form to help us better serve you. Did the information help you to achieve your goal? Yes No Don't know   Please provide us with comments to help improve this page:   How useful is the information? 1 2 3 4 5 Not useful Extremely useful

Back to top