From 3e313c2b3930b22edd43add9ecd817d16a77eb2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B6rn-Egil=20Dahlberg?= Date: Thu, 8 Mar 2012 10:41:58 +0100 Subject: doc: Enhance wording and remove typos --- erts/doc/src/erlang.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'erts/doc') diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index 239cc63f71..8c438b0bd7 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -4952,7 +4952,7 @@ true scheduler_wall_time

Returns a list of tuples with - {SchedulerId, ActiveTime, TotalTime}], where SchedulerId is an integer id of the scheduler, ActiveTime is + {SchedulerId, ActiveTime, TotalTime}, where SchedulerId is an integer id of the scheduler, ActiveTime is the duration the scheduler has been busy, TotalTime is the total time duration since scheduler_wall_time activation. The time unit is not defined and may be subject to change @@ -4965,7 +4965,9 @@ true scheduling (selecting) a process or port, meaning; executing process code, executing linked-in-driver or NIF code, executing built-in-functions or any other runtime handling, garbage collecting - or handling any other memory management. + or handling any other memory management. Note, a scheduler may also be + busy even if the operating system has scheduled out the scheduler + thread.

@@ -4973,7 +4975,7 @@ true scheduler_wall_time is turned off.

-

The list of scheduler information is unsorted and may come in different order +

The list of scheduler information is unsorted and may appear in different order between calls.

Using scheduler_wall_time to calculate scheduler utilization.

-- cgit v1.2.3