apart from memory size, i would like to know how much the app takes to initialize, lots of hmb deserialization, i would partition the whole domain in sub systems like bounded contexts in ddd, and i would build an application server offering services for its clients and this app server would use nh internally, that could be a good way to downsize this
On May 16, 11:12 am, Kyle <[email protected]> wrote: > We have just started to convert to NHibernate for our data access > layer. Our legacy database has roughly 400 tables with on average 125 > columns per table. Almost all tables have a composite key. Our > application is broken up into hundreds of smaller applications that > each have their own memory space. A normal user would use roughly 3-5 > applications at once time, and each application may access 15 - 20 > tables in a single session. > > So, here's my problem... Loading all the hbm.xml mapping files and > 400 domain objects during the BuildSessionFactory() call consumes > roughly 150 MB of memory per application before any data access > occurs. What can we do to lower the memory consumption? I'm pretty > new to NHibernate, so any advice would help. > > Thanks, > Kyle -- 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.
