Lines Matching refs:utilization

270 detect which CPU utilization mechanism to use on your platform you may
471 CPU utilization is an important, and alas all-too infrequently reported
474 will do its level best to report accurate CPU utilization figures, but
478    CPU utilization in netperf is reported as a value between 0 and 100%
480 utilization, netperf will report a metric called a "service demand".
481 The service demand is the normalization of CPU utilization and work
485 For both CPU utilization and service demand, lower is better.
492 platform-specific CPU utilization measurement mechanisms.  Single
500      The CPU utilization measurement mechanism was unknown to netperf or
501      netperf/netserver was not compiled to include CPU utilization
502      measurements. The code for the null CPU utilization mechanism can
506      An HP-UX-specific CPU utilization mechanism whereby the kernel
521      An HP-UX-specific CPU utilization mechanism whereby the kernel
532      A Solaris-specific CPU utilization mechanism whereby the kernel
599 available CPU utilization mechanism.  However, some platforms have no
606 utilization.
616 for many CPU utilization mechanisms.  In particular, the "PSTAT"
628    In summary, be sure to "sanity-check" the CPU utilization figures
642 The CPU utilization mechanisms used by netperf are "inline" in that
649 system.  As such, (m)any CPU utilization mechanisms used in the virtual
655 should not really trust CPU utilization figures reported by netperf or
659 mechanism, rather than rely on CPU utilization, one can rely instead on
745      This option will ask that CPU utilization and service demand be
746      calculated for the local system.  For those CPU utilization
749      40 seconds of time.  For those CPU utilization mechanisms
754      This option requests CPU utilization and service demand
849      throughput and CPU utilization are within +/- 2.5% of the "real"
989      for the *note CPU utilization: CPU Utilization. and service demand
1027      CPU utilization.  These items will be displayed as values which
1031      size or to obtain information such as CPU utilization is to employ
1155      Figure of Merit) is displayed.  If local *note CPU utilization:
1157      the local service demand.  Othersise, if remote CPU utilization is
1159      demand.  If neither local nor remote CPU utilization are requested
1250    CPU utilization can also affect the results of a bulk-transfer test.
1257 than 100% CPU utilization.  This can happen on an MP system where one
1505      means greater CPU utilization.
1580 lower CPU utilization and possibly higher throughput.  If it does not,
1865 the bulk-transfer performance (or rather, decrease the CPU utilization
1922 Such setups are distinguished by seriously low reported CPU utilization
2065 not matter which way the test is run, and the CPU utilization measured
2067 the CPU utilization mechanism being used may have some, well, issues
2068 measuring CPU utilization completely and accurately.
2211 utilization reporting and shows the asymmetry in CPU loading.  The `-T'
2360 utilization:
2375 advised, particularly when/if the CPU utilization approaches 100
2376 percent.  In the example above we see that the CPU utilization on the
2380 accuracy of similar CPU utilization implying little skew error is
2382 CPU systems if the utilization is reported as 100% or very close to it.
2385      system-wide CPU utilization.  When calculating the service demand
2438 system-wide CPU utilization.  When calculating the service demand each
3340      This will display the overall CPU utilization during the test as
3370      utilization. Units: single character denoting method.
3379      This will display the overall CPU utilization during the test as
3409      utilization. Units: single character denoting method.
3449      achieved for overall CPU utilization on the system running netperf
3450      (`LOCAL_CPU_UTIL') during the test, if CPU utilization measurement
3452      CPU utilization.
3456      achieved for overall CPU utilization on the system running
3457      netserver (`REMOTE_CPU_UTIL') during the test, if CPU utilization
3459      reported CPU utilization.
3541      The utilization of the CPU most heavily utilized during the test,
3544      utilization as reported by `LOCAL_CPU_UTIL' was low. Units: 0 to
3573      The utilization of the CPU most heavily utilized during the test,
3576      utilization as reported by `REMOTE_CPU_UTIL' was low. Units: 0 to
3999 Some of the CPU utilization measurement mechanisms of netperf work by
4003 arrive at a CPU utilization percentage.
4012    Thus, the netperf CPU utilization options `-c' and and `-C' can take
4033 instances of netperf.  It will report global CPU utilization and will
4035 CPU utilization.  So, you can use the CPU utilization reported by