Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix list rendering in MUC docs #4388

Merged
merged 1 commit into from
Oct 29, 2024
Merged

Fix list rendering in MUC docs #4388

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions doc/modules/mod_muc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -436,16 +436,17 @@ To address that problem MongooseIM has 2 levels of MUC rooms memory optimisation

### Room's process hibernation

By default the room's process is hibernated by the Erlang VM 90 seconds after the last activity.
By default, the room's process is hibernated by the Erlang VM 90 seconds after the last activity.
This timeout can be modified by `hibernate_timeout` option.

### Room deep hibernation

MongooseIM introduces an additional option of deep hibernation for unused rooms.
This optimisation works only for persistent rooms as only these can be restored on demand.
The improvement works as follows:

1. All room processes are traversed at a chosen `hibernated_room_check_interval`.
1. If a `hibernated_room_timeout` is exceeded, a "stop" signal is sent to a unused room.
1. If a `hibernated_room_timeout` is exceeded, a "stop" signal is sent to an unused room.
1. The room's process is stopped only if there are no online users or if the only one is its owner.
If the owner is online, a presence of a type unavailable is sent to it indicating that the room's process is being terminated.

Expand Down