Alex, I'm sorry if my response sounded less than humble. Such attitude has certainly crippled NHibernate for years, but my impression is that the current project leaders are very humble, helping and working hard to push NH to new heights.
There is a bit of technical debt, and certainly room for a lot of performance improvements. However, many problems with NH (large data sets, batch updating, SELECT N+1) comes from using it in ways it was not designed for. It very easy to fall into these traps, especially if NH is used in places where a small handmade DAL or a Micro-ORM (not really ORMs), such as PetaPoco, would be much better. I guess there are more pedagogic ways to say it, but if someone is loading thousands of entities into the UoW, there's a good chance that the problem would be better solved by redesigning the procedure or use a different tool /G 2012/3/20 Alex Norcliffe <[email protected]> > The general theme seems to be "performance is acceptable given the power > of NHibernate". I don't mean to be antagonising, but that's an unfair > summary of the problem. There are many other ORMs who have a comparable > featureset but with different performance characteristics, and for the rest > I'm not even aware of any quantitative analysis of the value of some of the > more tertiary features vs their performance impact. > > My point is not that someone use up their free time and respond > voluntarily to kick the ass out of the performance issue on this free > product. I work on an OSS project; it would be hypocritical (and we use > NHibernate). I'm talking about comms, and humility. It can lead to tickets > like this remaining untouched for years > https://nhibernate.jira.com/browse/NH-1365 > > @Harshil, for the moment if you're unhappy with NHibernate performance in > your scenario, take a look at something like PetaPoco > > *Alex Norcliffe* > Lead Architect, Umbraco 5 > Microsoft Regional Director > @alex_norcliffe <http://twitter.com/alex_norcliffe> on Twitter, blogging > at boxbinary.com > > On 20 March 2012 09:44, Mark Cranness <[email protected]> wrote: > >> On 19 March 2012 16:46, Chinna <[email protected]> wrote: >> > I have been evaluating the performance of NHibernate and ADO.NET. I >> > have created a test application which has an Employee table with >> > 75,000 records. When I try to get data using NHibernate it is very >> > slow compare to ADO.NET, it’s about 290% (approx.) slower. >> >> See: http://ormbattle.net/ , which reports a similar slowdown for >> NHibernate cf. SqlClient (see Performance scorecard > Multiple >> Operations > Create Instance). >> >> It's the price you pay for the power that an ORM gives. >> >> -- >> 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. >> >> > -- > 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. > -- 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.
