From 9c96967fbc6286f27b9be8b04afcfe34b362b2ef Mon Sep 17 00:00:00 2001
From: Sverker Eriksson
Date: Thu, 13 Sep 2018 15:53:06 +0200
Subject: stdlib: Update ets docs for write_concurrency and ordered_set
---
lib/stdlib/doc/src/ets.xml | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
(limited to 'lib/stdlib')
diff --git a/lib/stdlib/doc/src/ets.xml b/lib/stdlib/doc/src/ets.xml
index f8c54fb79a..0e67634d23 100644
--- a/lib/stdlib/doc/src/ets.xml
+++ b/lib/stdlib/doc/src/ets.xml
@@ -1135,11 +1135,22 @@ ets:select(Table, MatchSpec),
Functions that makes such promises over many objects (like
insert/2)
gain less (or nothing) from this option.
- Table type ordered_set is not affected by this option.
- Also, the memory consumption inflicted by
- both write_concurrency and read_concurrency is a
- constant overhead per table. This overhead can be especially
- large when both options are combined.
+ The memory consumption inflicted by both write_concurrency
+ and read_concurrency is a constant overhead per table for
+ set, bag and duplicate_bag. For
+ ordered_set the memory overhead depends on the number
+ of inserted objects and the amount of actual detected
+ concurrency. The memory overhead can be especially large when both
+ options are combined.
+
+ Prior to stdlib-3.7 (OTP-22.0) write_concurrency had no
+ effect on ordered_set.
+ The current implementation of write_concurrency for
+ ordered_set does only improve explicit single key
+ operations. Mixing single key operations with operations
+ potentially accessing multiple keys may even yield worse
+ performance with write_concurrency on ordered_set.
+
{read_concurrency,boolean()}
--
cgit v1.2.3