From ad39b74bfc30d532a622d693bc4a182becfa5471 Mon Sep 17 00:00:00 2001
From: Rickard Green
Date: Wed, 14 Jun 2017 17:54:29 +0200
Subject: Update documentation of ERL_MAX_ETS_TABLES
---
lib/stdlib/doc/src/ets.xml | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
(limited to 'lib')
diff --git a/lib/stdlib/doc/src/ets.xml b/lib/stdlib/doc/src/ets.xml
index 342be80f98..f6f3d18d6a 100644
--- a/lib/stdlib/doc/src/ets.xml
+++ b/lib/stdlib/doc/src/ets.xml
@@ -49,13 +49,22 @@
associated with each key. A bag or duplicate_bag table can
have many objects associated with each key.
- The number of tables stored at one Erlang node is limited.
- The current default limit is about 1400 tables. The upper
- limit can be increased by setting environment variable
- ERL_MAX_ETS_TABLES before starting the Erlang runtime
- system (that is, with option -env to
- erl/werl). The actual limit can be slightly higher
- than the one specified, but never lower.
+
+
+ The number of tables stored at one Erlang node used to
+ be limited. This is no longer the case (except by memory usage).
+ The previous default limit was about 1400 tables and
+ could be increased by setting the environment variable
+ ERL_MAX_ETS_TABLES before starting the Erlang runtime
+ system. This hard limit has been removed, but it is currently
+ useful to set the ERL_MAX_ETS_TABLES anyway. It should be
+ set to an approximate of the maximum amount of tables used. This since
+ an internal table for named tables is sized using this value. If
+ large amounts of named tables are used and ERL_MAX_ETS_TABLES
+ hasn't been increased, the performance of named table lookup will
+ degrade.
+
+
Notice that there is no automatic garbage collection for tables.
Even if there are no references to a table from any process, it
--
cgit v1.2.3