After upgrading my prosody instance to 0.9.7, it started slowly consuming more and more CPU time. It was already consuming more and more RAM (see #461), so the CPU time consumption is probably not directly related to the memory leak.
As I had to restart it due to CVE-2015-0235, I will have to wait some more weeks before being able to provide hard numbers on which functions are burning the time.
Thanks for the report! I had seen this behaviour on another server too, apparently it's not an isolated case.
Will investigate...
Changes
tags Milestone-0.9 Status-Accepted
owner MattJ
stephan.adler
on
I can confirm this issue for two different prosody instances. Both instances use the Debian-Packages of prosody and lua-sec-prosody for debian wheezy.
Versions:
lua-sec-prosody = 0.5.1-2~wheezy
lua-event = 0.4.3-5~wheezy
storage is internal in both cases.
stephan.adler
on
I forgot to include my munin stats in my confirmation. Here they are.
After upgrading my prosody instance to 0.9.7, it started slowly consuming more and more CPU time. It was already consuming more and more RAM (see #461), so the CPU time consumption is probably not directly related to the memory leak. As I had to restart it due to CVE-2015-0235, I will have to wait some more weeks before being able to provide hard numbers on which functions are burning the time.
AttachmentsThanks for the report! I had seen this behaviour on another server too, apparently it's not an isolated case. Will investigate...
ChangesI can confirm this issue for two different prosody instances. Both instances use the Debian-Packages of prosody and lua-sec-prosody for debian wheezy. Versions: lua-sec-prosody = 0.5.1-2~wheezy lua-event = 0.4.3-5~wheezy storage is internal in both cases.
I forgot to include my munin stats in my confirmation. Here they are.
Attachments@stephan Both your graphs are memory increases. Do you also have CPU increases? What are you using to collect the stats?
Does this still happen? Does it happen with 0.10?
ChangesI have heard no reports of this or #461 in a long time, let's assume that it's fixed in 0.10 somehow.
Changes