diff options
| author | Badlop <badlop@process-one.net> | 2008-01-08 16:11:58 +0000 |
|---|---|---|
| committer | Badlop <badlop@process-one.net> | 2008-01-08 16:11:58 +0000 |
| commit | 635978b137cdbf999d219f6546eae307e26691d9 (patch) | |
| tree | a79e2d1d9b6875e37cfb865da1e797a2f3e04ec2 /src/ejabberdctl.cfg.example | |
| parent | fix version.tex generation bug (diff) | |
* src/ejabberdctl.template: Removed the option ERL_FULLSWEEP_AFTER
because it is almost useless regarding ejabberd's performance.
* src/ejabberdctl.cfg.example: Likewise
SVN Revision: 1140
Diffstat (limited to 'src/ejabberdctl.cfg.example')
| -rw-r--r-- | src/ejabberdctl.cfg.example | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/src/ejabberdctl.cfg.example b/src/ejabberdctl.cfg.example index eb763e61d..91f50346d 100644 --- a/src/ejabberdctl.cfg.example +++ b/src/ejabberdctl.cfg.example @@ -61,20 +61,6 @@ # #ERL_MAX_ETS_TABLES=1400 -# ERL_FULLSWEEP_AFTER: Maximum number of collections before a forced fullsweep -# -# To reduce memory usage, you can set environment variable ERL_FULLSWEEP_AFTER. -# But in this case ejabberd may work slower. -# -# The ERL_FULLSWEEP_AFTER option shrinks the size of the Erlang process after -# RAM intensive events. Note that this option may downgrade performance. Hence -# this option is only interesting on machines that also host other services -# (webserver, mail) on which ejabberd does not receive constant load. -# -# Default: 65535 -# -#ERL_FULLSWEEP_AFTER=65536 - # The next variable allows to explicitly specify erlang node for ejabberd # It can be given in different formats: # ERLANG_NODE=ejabberd |