Mercurial > prosody-modules

comparison mod_log_events_by_memory/README.markdown @ 3618:f781a90018f4

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_log_events_by_memory: Add link to post explaining different kinds of memory leaks
author Kim Alvefur <zash@zash.se>
date Thu, 13 Jun 2019 00:25:12 +0200
parents 61b9c89db212
children
comparison
equal deleted inserted replaced
3617:61b9c89db212 3618:f781a90018f4
4 4
5 ``` lua 5 ``` lua
6 log_memory_threshold = 20*1024 6 log_memory_threshold = 20*1024
7 ``` 7 ```
8 8
9 If you are looking to identify memory leaks, please first read [Three
10 kinds of memory
11 leaks](https://blog.nelhage.com/post/three-kinds-of-leaks/).
12
9 Prosody runs on Lua which uses automatic memory management with garbage 13 Prosody runs on Lua which uses automatic memory management with garbage
10 collection, so the numbers reported by this module are very likely to be 14 collection, so the numbers reported by this module are very likely to be
11 useless for the purpose of identifying memory leaks. Large, but 15 useless for the purpose of identifying memory leaks. Large, but
12 temporary, increases in memory usage can however highlight other kinds 16 temporary, increases in memory usage can however highlight other kinds
13 of performance problems and sometimes even provide hits for where to 17 of performance problems and sometimes even provide hits for where to