diff options
| author | Sverker Eriksson <[email protected]> | 2018-10-31 16:31:34 +0100 |
|---|---|---|
| committer | GitHub <[email protected]> | 2018-10-31 16:31:34 +0100 |
| commit | fa6994f5c8384a15196121fce2983291c9c21245 (patch) | |
| tree | 0b01c4e37ce21c5863d7607214ca097445ed673d /lib/stdlib/doc | |
| parent | a03b0b0298208216481fdc2a373e5cda893535d2 (diff) | |
| parent | cc18836780d7d047bf53b1ff8d94a6b31b58f98a (diff) | |
| download | otp-fa6994f5c8384a15196121fce2983291c9c21245.tar.gz otp-fa6994f5c8384a15196121fce2983291c9c21245.tar.bz2 otp-fa6994f5c8384a15196121fce2983291c9c21245.zip | |
Merge PR-1997 from sverker/erts/ordered_set-select-improvements/OTP-15325
Even more scalable ETS ordered_set with write_concurrency
Diffstat (limited to 'lib/stdlib/doc')
| -rw-r--r-- | lib/stdlib/doc/src/ets.xml | 14 |
1 files changed, 4 insertions, 10 deletions
diff --git a/lib/stdlib/doc/src/ets.xml b/lib/stdlib/doc/src/ets.xml index 57a19ef2ca..611b176613 100644 --- a/lib/stdlib/doc/src/ets.xml +++ b/lib/stdlib/doc/src/ets.xml @@ -611,9 +611,8 @@ Error: fun containing local Erlang function calls </item> <item> <p><c>Item=stats, Value=tuple()</c></p> - <p>Returns internal statistics about <c>set</c>, <c>bag</c>, and - <c>duplicate_bag</c> tables on an internal format used by OTP - test suites. Not for production use.</p></item> + <p>Returns internal statistics about tables on an internal format + used by OTP test suites. Not for production use.</p></item> </list> </desc> </func> @@ -1140,16 +1139,11 @@ ets:select(Table, MatchSpec),</code> <c>set</c>, <c>bag</c> and <c>duplicate_bag</c>. For <c>ordered_set</c> 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.</p> + concurrency in runtime. The memory overhead can be especially + large when both options are combined.</p> <note> <p>Prior to stdlib-3.7 (OTP-22.0) <c>write_concurrency</c> had no effect on <c>ordered_set</c>.</p> - <p>The current implementation of <c>write_concurrency</c> for - <c>ordered_set</c> does only improve explicit single key - operations. Mixing single key operations with operations - potentially accessing multiple keys may even yield worse - performance with <c>write_concurrency</c> on <c>ordered_set</c>.</p> </note> <marker id="new_2_read_concurrency"></marker> </item> |