Lines Matching refs:utilization

299 detect which CPU utilization mechanism to use on your platform you may
518 CPU utilization is an important, and alas all-too infrequently
522 CPU utilization figures, but some combinations of processor, OS and
525 CPU utilization in netperf is reported as a value between 0 and 100%
527 utilization, netperf will report a metric called a @dfn{service
528 demand}.  The service demand is the normalization of CPU utilization
532 transaction.   For both CPU utilization and service demand, lower is
541 platform-specific CPU utilization measurement mechanisms.  Single
550 The CPU utilization measurement mechanism was unknown to netperf or
551 netperf/netserver was not compiled to include CPU utilization
552 measurements. The code for the null CPU utilization mechanism can be
555 An HP-UX-specific CPU utilization mechanism whereby the kernel
568 An HP-UX-specific CPU utilization mechanism whereby the kernel
578 A Solaris-specific CPU utilization mechanism whereby the kernel keeps
637 CPU utilization mechanism.  However, some platforms have no
644 CPU utilization.
654 for many CPU utilization mechanisms.  In particular, the ``PSTAT''
666 In summary, be sure to ``sanity-check'' the CPU utilization figures
677 The CPU utilization mechanisms used by netperf are ``inline'' in that
684 iron system.  As such, (m)any CPU utilization mechanisms used in the
690 should not really trust CPU utilization figures reported by netperf or
694 mechanism, rather than rely on CPU utilization, one can rely instead
786 This option will ask that CPU utilization and service demand be
787 calculated for the local system.  For those CPU utilization mechanisms
790 For those CPU utilization mechanisms requiring no calibration, the
796 This option requests CPU utilization and service demand calculations
903 throughput and CPU utilization are within +/- 2.5% of the ``real''
1047 @ref{CPU Utilization,CPU utilization} and service demand calculations.
1085 retrieve such interesting remote information as CPU utilization.
1090 size or to obtain information such as CPU utilization is to employ
1235 utilization} is requested via the @option{-c} option then the SFM is
1236 the local service demand.  Othersise, if remote CPU utilization is
1238 service demand.  If neither local nor remote CPU utilization are
1331 CPU utilization can also affect the results of a bulk-transfer test.
1338 than 100% CPU utilization.  This can happen on an MP system where one
1615 data transferred, which means greater CPU utilization.
1692 _should_ result in lower CPU utilization and possibly higher
1966 utilization of a bulk-transfer test).  This sensitivity is most acute
2021 Such setups are distinguished by seriously low reported CPU utilization
2181 should not matter which way the test is run, and the CPU utilization
2183 suggests that the CPU utilization mechanism being used may have some,
2184 well, issues measuring CPU utilization completely and accurately.
2334 enable CPU utilization reporting and shows the asymmetry in CPU
2484 CPU utilization:
2501 not advised, particularly when/if the CPU utilization approaches 100
2502 percent.  In the example above we see that the CPU utilization on the
2506 accuracy of similar CPU utilization implying little skew error is
2508 CPU systems if the utilization is reported as 100% or very close to
2513 system-wide CPU utilization.  When calculating the service demand
2566 system-wide CPU utilization.  When calculating the service demand each
3476 This will display the overall CPU utilization during the test as
3500 utilization. Units: single character denoting method.
3507 This will display the overall CPU utilization during the test as
3531 utilization. Units: single character denoting method.
3562 achieved for overall CPU utilization on the system running netperf
3563 (@code{LOCAL_CPU_UTIL}) during the test, if CPU utilization measurement
3565 utilization.
3568 achieved for overall CPU utilization on the system running netserver
3569 (@code{REMOTE_CPU_UTIL}) during the test, if CPU utilization
3571 reported CPU utilization.
3637 The utilization of the CPU most heavily utilized during the test, as
3639 multi-CPU system was saturated even though the overall CPU utilization
3661 The utilization of the CPU most heavily utilized during the test, as
3663 multi-CPU system was saturated even though the overall CPU utilization
3979 Some of the CPU utilization measurement mechanisms of netperf work by
3983 arrive at a CPU utilization percentage.
3992 Thus, the netperf CPU utilization options @option{-c} and and
4017 utilization and will calculate service demand believing it was the
4018 only thing causing that CPU utilization.  So, you can use the CPU
4019 utilization reported by netperf in an aggregate test, but you have to