The HBM objects still require serializing to XML, it's the meta classes that don't; however, those classes are a *nightmare* to work with. The issue we also have is XML is the public, backwards-compatible, interface to NH, the meta classes are subject to change at any time; this makes FNHs integration with NH much more brittle. There have been some performance optimisations done for 1.0, for example we're able to merge all your mappings before passing them to NH, this has a noticeable performance increase for larger systems (negligible for smaller ones); we've also got a patch for serializing the configuration, but I'm not sure if that'll make 1.0 yet.
The thing is, performance really shouldn't be that much of a concern. Yes, NHibernate can be slow when validating your XML, but it's only a one-off thing at the start of your application; if you're in a windows environment then I can understand you might want to speed it up, but in a web app it all happens behind the scenes anyway. 2009/8/13 Asbjørn Ulsberg <[email protected]> > > Wasn't there talk about building HBM objects directly instead of going > through the XML files (that need the painstakingly slow validation)? Won't > that speed things up quite a bit, and isn't that a change independent of > NH? > > > -Asbjørn > > > On Thu, 23 Jul 2009 12:16:15 +0200, James Gregory > <[email protected]> wrote: > > > Depends :) It's down to NH, not FNH really. NH takes quite a while to > > validate what we give it. > > Do your unit tests need the entire domain? If not you could build a > > separate > > PersistenceModel instance with just the classes you need in. > > > > In our model branch (which will become 1.0 in the not-too-distant future) > > we've implemented merging of mappings, which speeds up BuildConfiguration > > when there's a lot of mappings. > > > > On Thu, Jul 23, 2009 at 11:07 AM, Mikael Henriksson > > <[email protected]>wrote: > > > >> Is it possible to tweak the configuration part for performance somehow? > >> Now > >> that the number of classes increased unit testing has become a bitch. It > >> takes forever to do .BuildConfiguration(). Is there something I can do > >> to > >> improve this time? When it's deployed I don't give a rats ass but while > >> I > >> run my tests etc it has become sort of annoying! > >> > >> > > >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
