aboutsummaryrefslogtreecommitdiffstats
path: root/system/doc/efficiency_guide
diff options
context:
space:
mode:
authorBjörn-Egil Dahlberg <[email protected]>2017-01-20 14:12:18 +0100
committerBjörn-Egil Dahlberg <[email protected]>2017-01-20 14:12:18 +0100
commit6912c3db95b4ca0d78b5c388daae262321645624 (patch)
treed626d6550b4bf9f10622a217f377c91c1740668f /system/doc/efficiency_guide
parent05ff91af1870f64ce7a301ee71a245adeb89e249 (diff)
downloadotp-6912c3db95b4ca0d78b5c388daae262321645624.tar.gz
otp-6912c3db95b4ca0d78b5c388daae262321645624.tar.bz2
otp-6912c3db95b4ca0d78b5c388daae262321645624.zip
otp: Don't mention percept in documentation
Diffstat (limited to 'system/doc/efficiency_guide')
-rw-r--r--system/doc/efficiency_guide/processes.xml4
1 files changed, 0 insertions, 4 deletions
diff --git a/system/doc/efficiency_guide/processes.xml b/system/doc/efficiency_guide/processes.xml
index f2d9712f51..b9982353be 100644
--- a/system/doc/efficiency_guide/processes.xml
+++ b/system/doc/efficiency_guide/processes.xml
@@ -261,10 +261,6 @@ true
The estone benchmark, for example, is entirely sequential. So is
the most common implementation of the "ring benchmark"; usually one process
is active, while the others wait in a <c>receive</c> statement.</p>
-
- <p>The <seealso marker="percept:percept">percept</seealso> application
- can be used to profile your application to see how much potential (or lack
- thereof) it has for concurrency.</p>
</section>
</chapter>