On Jun 8, 2012, at 10:16 PM, Glyph wrote: Hey Glyph. thanks for your comments.
Do you know what causes its memory to grow? We're working on addressing a similar condition and the more data we can get, the better. Are you scheduling meetings with large numbers of people? Do you have a lot of events that repeat very frequently?
Yes we are around 70 users in caldav. i would say around 30 users has a lot of events every day. we also have scheduled events that repeats for example every week. These events contains a lot of attendees, more than 30. i will ask our administrator what we have configured to attend more users than the default is. (not sure if we changed something in a plist file to attend a lot of users, or if we use groups for that..) some more information: before some days our error.log file was growing vey fast. It looked like there was a kind of loop-logging with this reoccurring lines. 2012-05-31 16:12:00+0200 [-] [caldav-6] BEGIN:VALARM 2012-05-31 16:12:00+0200 [-] [caldav-6] ACTION:AUDIO 2012-05-31 16:12:00+0200 [-] [caldav-6] ATTACH:Basso 2012-05-31 16:12:00+0200 [-] [caldav-6] TRIGGER:-PT15M 2012-05-31 16:12:00+0200 [-] [caldav-6] X-WR-ALARMUID:E73FEE8D-B0E0-4F97-A3BA-DEDBB950054F 2012-05-31 16:12:00+0200 [-] [caldav-6] END:VALARM In 14 seconds we had 28.493 repeating errors, thats around 2035 6-liners per second we thought that this error log was related to the out of memory. but now we have the out of memory without these error log lines.
The important question is how we can restrict the memory usage for every caldav process?
You can't, really; sorry. It's a bug that it takes so much memory.
Ok. we killed those processes manually (our administrator had funny nights ;)) but yesterday we starts to write a script that monitor the caldav workers and kill those processes when they running out of memory. Many thanks for your comments! Would be great when you have more informations or hints what we can do to avoid this. Marko