Top Values of a Partition Resource

The following examples show how the op.top operation handles partitioned SSIDs. The following example shows the number of bytes sent by each listed application.

$ sstore capture //:class.net/ip//:stat.out-bytes//:part.application
2016-05-18T12:18:55  //:class.net/ip//:stat.out-bytes//:part.application
                    sshd: 332648.0
                    httpd: 0.0
                    sched: 79741.0
                    nscd: 604.0
                    pkg: 0.0
                    extract_boot_fil: 0.0
                    grub-mkconfig: 0.0
                    00_header: 0.0
                    nfsmapid: 399.0
                    grub-install: 0.0
                    ntpd: 448.0
                    ldap_cachemgr: 3051.0
2016-05-18T12:18:56  //:class.net/ip//:stat.out-bytes//:part.application
                    sshd: 348264.0
                    httpd: 0.0
                    sched: 86397.0
                    nscd: 604.0
                    pkg: 5302.0
                    extract_boot_fil: 0.0
                    grub-mkconfig: 0.0
                    00_header: 0.0
                    nfsmapid: 399.0
                    grub-install: 0.0
                    ntpd: 448.0
                    ldap_cachemgr: 3051.0

The following sstore capture command reduces the data to just the largest three partition key values at each data point.

$ sstore capture //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
2016-05-18T12:18:55  //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
                    sshd: 332648.0
                    sched: 79741.0
                    ldap_cachemgr: 3051.0
2016-05-18T12:18:56  //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
                    sshd: 348264.0
                    sched: 86397.0
                    pkg: 5302.0

The sstore export command determines the top values of each partition key over the entire period for which data are available and then compares those top values for each key to determine the top keys over the entire period. Thus the sstore export command shows the same partition keys at each time stamp, even if the key has a zero value at some points. In the preceding sstore capture results, the ldap_cachemgr key has the third largest value of all the partition keys at time 12:18:55. The sstore export results at that same time report the value of the pkg key because over the entire time period, the sshd, sched, and pkg keys have the highest values. The sstore export results show these same three keys in this same order at all data points.

$ sstore export //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
2016-05-18T12:18:55  //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
                    sshd: 332648.0
                    sched: 79741.0
                    pkg: 0.0
2016-05-18T12:18:56  //:class.net/ip//:stat.out-bytes//:part.application//:op.top(3)
                    sshd: 348264.0
                    sched: 86397.0
                    pkg: 5302.0

If a single SSID specifies both partitioned SSIDs and non-partitioned SSIDs, partitioned SSIDs are ignored. The following command records only values for //:class.proc//:res.*//:stat.cpu-percentage; no values are recorded for //:class.net/ip//:stat.out-bytes//:part.application:

$ sstore capture \
> //:s.[//:class.proc//:res.*//:stat.cpu-percentage,//:class.net/ip//:stat.out-bytes//:part.application]//:op.top

If you specify multiple non-partitioned SSIDs in a single SSID for op.top, all data values are compared together to determine the top values. Possibly the values of one of the component SSIDs will not appear in the op.top results.