Agreed -- if raw DB access performance is your overriding criteria for a data-access technology, NO o/rm is the answer here (EF, NH, or otherwise); you are using a scalpel when what you need is a chainsaw.
That said, I think its also demonstrably true that NH offers the flexibility of implementation + configuration that will allow it to perform competitively against just about any other o/rm quite capably -- but this whole class of product will never outperform raw data-access strategies in any way; it just wasnt designed to solve that class of problem. -Steve B. -----Original Message----- From: Fabio Maulo <[email protected]> Date: Thu, 12 Feb 2009 11:10:34 To: <[email protected]> Subject: [nhibernate-development] Re: Loading related data gives lousy performance 2009/2/12 Chucara <[email protected]> > > > Fabio Maulo: > > Without actually attaching the related data to the main data, it takes > 3 seconds to load the 110,000 rows. So less than 4 seconds all in all > is my best estimate. It's a lot faster, but it also a lot more work. This is not comparable... for that I said "loading a similar DataSets (mean same info of main+related entities)".What I do in some cases, where possible, is load a plain-DTO (not an obj graph) using HQL or SQL, then I load the obj-graph of a sigle entity when the user want edit something specific. BTW if you really need to load such kind of infos amount, NH is NOT what you are looking for. Try something else using pure ADO.NET and all feature available in you specific DataProvider implementation. -- Fabio Maulo
