From 5ca9e5b8b990f7539a3e312fa33e09bd21c228c0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn-Egil=20Dahlberg?=
Date: Thu, 8 Mar 2012 10:16:54 +0100
Subject: doc: Rewording of scheduler_wall_time
---
erts/doc/src/erlang.xml | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
(limited to 'erts/doc/src')
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 922d20bb82..cd95a6a312 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -4939,7 +4939,8 @@ true
{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.
+ activation. The time unit is not defined and may be subject to change
+ between releases, operating systems and system restarts.
scheduler_wall_time should only be used to calculate relative
values for scheduler-utilization. ActiveTime can never exceed TotalTime.
@@ -4947,7 +4948,8 @@ true
The definition of a busy scheduler is when it is not idle or not
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.
+ built-in-functions or any other runtime handling, garbage collecting
+ or handling any other memory management.
@@ -4980,7 +4982,7 @@ ok
{7,0.973237033077876},
{8,0.9741297293248656}]
-
Using the same snapshot to calculate a total scheduler-utilization.
+
Using the same snapshots to calculate a total scheduler-utilization.