ejabberd - Comments for "[New] history_size and other settings" https://www.ejabberd.im/node/16997 en The muc_room table stores the https://www.ejabberd.im/node/16997#comment-63317 <p>The muc_room table stores the room information that changes infrequently: the room options.<br /> The room information that is expected to change frequently, is kept only in the room process state: occupants, history, etc.<br /> And the table muc_online_room allows to find the room process.</p> <p>All this is for efficiency reasons.</p> <p>One way to keep being efficient and still keep room history between service restarts would be to implement this feature request:<br /> <noindex><a href="https://support.process-one.net/browse/EJAB-1145" title="https://support.process-one.net/browse/EJAB-1145" rel="nofollow" >https://support.process-one.net/browse/EJAB-1145</a></noindex></p> Fri, 31 Jan 2014 12:45:49 +0000 mfoss comment 63317 at https://www.ejabberd.im Will it make any sense to https://www.ejabberd.im/node/16997#comment-63315 <p>Will it make any sense to change the muc_room value to "Disk only"? Will this make any difference?</p> Fri, 31 Jan 2014 12:33:46 +0000 xmpp_noob comment 63315 at https://www.ejabberd.im I think it measures number of https://www.ejabberd.im/node/16997#comment-63314 <p>I think it measures number of messages.</p> <p>Room history is kept only in the room process state, that is in RAM. So, it's lost when the room gets recreated, and that happens when mod_muc is restarted.</p> Fri, 31 Jan 2014 12:30:50 +0000 mfoss comment 63314 at https://www.ejabberd.im