Mercurial > prosody-modules
view mod_log_events_by_memory/README.markdown @ 4719:5a06c711649c
mod_bookmarks2: Use max_items='max' on trunk, with fallback
check_node_config() throws an error attempting to compare the
pep_max_items number with the 'max' string, which allows detecting and
support using 'max' where available.
Unsure what happens when you upgrade, that seems a problem for a future
commit! :)
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 20 Oct 2021 22:16:14 +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.