mirror of
https://github.com/processone/ejabberd
synced 2025-10-03 01:39:35 +02:00
* 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
This commit is contained in:
parent
74d52708b0
commit
635978b137
3 changed files with 7 additions and 17 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue