My guild is trying to settle on an ingame event manager to handle signups event creation etc.
We currently are using GEM but we have a few members that are having apparently insurmountable issues with it (constant errors) so we'd like to move to something else.
I recently looked at GroupCalendar to give it a go and it seems perfect in every way except:
With GroupCalendar installed I get huge average increasing memory usage rate. Typically (with GEM (actively communicating) and many many other mods installed) I see around .2 to .7 kibs average increasing rate (not in raid), with GroupCalendar active and communicating it jumps to around 7 to 12 kibs. I am under the impression that this causes far more frequent garbage collects and subsequent temporary frame freezes.
Does anyone know what is causing GroupCalendar to behave in this fashion? Is there anything I can do as a user?
Would installing TekSupport help me determine what the deal is?
And last, does anyone know of a third alternative to either GEM or GC?
 I would like to note that the author of GC is aware of the increasing memory rate issue and is in theory working on it...but I'm not sure I have a lot of faith in a fix because of this response:
> use the Titan Bar mod, one of the options is a mod memory monitor. When I upgraded to Calendar 3.0.3 I started noticing a constant increase in the memory allocated.
That's correct, LUA is designed so that scripts consume memory and don't release it immediately. The language periodically goes through and gathers it back in what's called "garbage collection". This is normal behavior for LUA.
Also the members having issues with GEM have been in contact with that author and are unable to get anything solved :(