Hi Tuna: Serialization doesnt reduce memory but atleast I can unload the assemblies which were loaded for "AddAssembly" by unloading the appdomain.
Fabio We are following one session per workflow and single sessionfactory approach Having said that is it a good idea to move towards NH 2.1 and use 2.1 trunk code in production? Thanks On May 4, 1:47 am, Fabio Maulo <[email protected]> wrote: > about memory "consumption" in your desktop app....which is the pattern of > the session life time ? > > 2009/5/3 codegoblin <[email protected]> > > > > > > > Hi > > > Currently we are using Nhibernate 1.2.1 with a desktop application > > but we have realized that the memory footprint of our application has > > gone up. So one of our plans to mitigate this issue was to build the > > configuration in different appdomain and unload it. But turns out I > > cant serialize configuration in NH 1.2..1 and it is serializable in > > 2.1 . Our application has made a heavy use of Interceptor from NH > > 1.2.1 which I think would be deprecated further. > > > Based on these facts can I just upgrade from 1.2 to 2.1 to avail the > > config serialization possibility. Or is there a patch available for > > 1.2.1 . Or is ver 2.1 still not production stable. > > > Thanks > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
