We currently use NHibernate with over 450 mapped entities to a legacy database and that number should double soon.
We did slight performance optimization to speed up startup, and that included concatenating all hbm.xml files into one single hbm.xml during the build process, this lessens the amount of Validation calls on the xml. Ayende wrote an article to this affect: http://ayende.com/Blog/archive/2007/10/26/Real-World-NHibernate-Reducing-startup-times-for-large-amount-of.aspx We also use NHProxyGen to generate static proxies which takes ~10 minutes at build time but greatly improves performance during run time (at least during the first couple of hits then performance is same as dynamic proxies). There are a few gotcha's to look for when mapping against a legacy database, especially when you are using identity columns everywhere, but the lesson there is to not be afraid to change schema to work better with NHibernate, and most of the time legacy schema is just bad to begin with (outsourcers, neglect, etc...). And then you can polish it off with NHProf to really get things cooking. NHibernate scales very well. Joe On Mar 4, 5:07 am, Thomas Koch <[email protected]> wrote: > Hi - we have a legacy web application which is to be ported to use > NHibernate 2.0. > > My question is whether or not some you have any experience with using > NHibernate on a web-application with approx. 240 tables? The 240 > tables is including both many-to-many tables and entity tables. > > Does it scale? Can I expect the initial load time to explode to 20 > minutes or what? > > Cheers, > Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
