Mercurial > prosody-modules
view mod_log_events_by_memory/README.markdown @ 4942:e7b9bc629ecc
mod_rest: Add special handling to catch MAM results from remote hosts
Makes MAM queries to remote hosts works.
As the comment says, MAM results from users' local archives or local
MUCs are returned via origin.send() which is provided in the event and
thus already worked. Results from remote hosts go via normal stanza
routing and events, which need this extra handling to catch.
This pattern of iq-set, message+, iq-result is generally limited to MAM.
Closest similar thing might be MUC join, but to really handle that you
would need the webhook callback mechanism.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 16 May 2022 19:47:09 +0200 |
parents | f781a90018f4 |
children |
line wrap: on
line source
This module compares the memory usage reported by Lua before and after each event and reports it to the log if it exceeds the configuration setting `log_memory_threshold` (in bytes). ``` lua log_memory_threshold = 20*1024 ``` If you are looking to identify memory leaks, please first read [Three kinds of memory leaks](https://blog.nelhage.com/post/three-kinds-of-leaks/). Prosody runs on Lua which uses automatic memory management with garbage collection, so the numbers reported by this module are very likely to be useless for the purpose of identifying memory leaks. Large, but temporary, increases in memory usage can however highlight other kinds of performance problems and sometimes even provide hits for where to look for memory leaks.