Thanks Jason. I didn't know if there was perhaps something fundamentally wrong with how we're handling object lifecycle.. that fully disposing of objects between each active run would be a better approach. It's an ETL application, triggered by MSMQ messages and running through a standard process of objects such as PreLoadChecks, LoadSteps, and PostLoadChecks (for example, there are more). So we iterate through each of these objects on each trigger and run their Execute method. If there is nothing fundamentally wrong with keeping the objects "alive" then I need to research more into what objects are not releasing their memory after use and this is not a problem with how we're using Windsor. Just wanted to rule that out.
On Sat, Feb 12, 2011 at 3:57 PM, Jason Meckley <[email protected]>wrote: > there isn't much to go on here. 75MB isn't that much for a .net windows > service. as a base line create an empty windows service is start it and > check memory consumption. then add an empty windsor container and see what > the memory usage is. > > it's difficult to say what the cause of 500+ MB without a better > understanding of application and structure. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
