diff options
| author | Björn Gustavsson <[email protected]> | 2017-05-17 12:31:08 +0200 |
|---|---|---|
| committer | GitHub <[email protected]> | 2017-05-17 12:31:08 +0200 |
| commit | dfa81717e0e5b07eaecae536523c820368e900de (patch) | |
| tree | 7a67aac8a02b3559ad48c96aa2cb43bf519a4eac /lib/tools/doc/src/lcnt_chapter.xml | |
| parent | 79fd4b7c7b77330accae77f0ff90843ea5aed20d (diff) | |
| parent | 836d9bacfbea741d53e8f007c6a5e0ad37e7bd34 (diff) | |
| download | otp-dfa81717e0e5b07eaecae536523c820368e900de.tar.gz otp-dfa81717e0e5b07eaecae536523c820368e900de.tar.bz2 otp-dfa81717e0e5b07eaecae536523c820368e900de.zip | |
Merge pull request #1465 from bjorng/bjorn/tools/fix-lcnt-doc
Fix a few minor issues in the lcnt documentation
Diffstat (limited to 'lib/tools/doc/src/lcnt_chapter.xml')
| -rw-r--r-- | lib/tools/doc/src/lcnt_chapter.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/tools/doc/src/lcnt_chapter.xml b/lib/tools/doc/src/lcnt_chapter.xml index 362f212963..1981d66117 100644 --- a/lib/tools/doc/src/lcnt_chapter.xml +++ b/lib/tools/doc/src/lcnt_chapter.xml @@ -42,7 +42,7 @@ completed its access to the resource and unlocked it. The <c>lcnt</c> tool measures these lock conflicts. </p> <p> - Locks has an inherent cost in execution time and memory space. It takes time initialize, destroy, aquiring or releasing locks. To decrease lock contention it + Locks have an inherent cost in execution time and memory space. It takes time initialize, destroy, aquiring or releasing locks. To decrease lock contention it some times necessary to use finer grained locking strategies. This will usually also increase the locking overhead and hence there is a tradeoff between lock contention and overhead. In general, lock contention increases with the number of threads running concurrently. The <c>lcnt</c> tool does not measure locking overhead. </p> @@ -67,7 +67,7 @@ Erlang/OTP 20 [erts-9.0] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe <p>Once you have a lock counting enabled VM the module <c>lcnt</c> can be used. The module is intended to be used from the current running nodes shell. To access remote nodes use <c>lcnt:clear(Node)</c> and <c>lcnt:collect(Node)</c>. </p> <p>All locks are continuously monitored and its statistics updated. Use <c>lcnt:clear/0</c> to initially clear all counters before running any specific tests. This command will also reset the duration timer internally.</p> - <p>To retrieve lock statistics information use, <c>lcnt:collect/0,1</c>. The collect operation will start a <c>lcnt</c> server if it not already started. All collected data will be built into an erlang term and uploaded to the server and a duration time will also be uploaded. This duration is the time between <c>lcnt:clear/0,1</c> and <c>lcnt:collect/0,1</c>.</p> + <p>To retrieve lock statistics information, use <c>lcnt:collect/0,1</c>. The collect operation will start a <c>lcnt</c> server if it not already started. All collected data will be built into an Erlang term and uploaded to the server and a duration time will also be uploaded. This duration is the time between <c>lcnt:clear/0,1</c> and <c>lcnt:collect/0,1</c>.</p> <p>Once the data is collected to the server it can be filtered, sorted and printed in many different ways.</p> <p>See the <seealso marker="lcnt">reference manual</seealso> for a description of each function.</p> |