Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
Your profile
Tag cloud
.net asp.net asp.net mvc azure book bug business intelligence c# cloud computing database dates excel functions gemini google gotcha how to howto iis indexing interview jquery kanban linq measurement mvc nhibernate nunit performance programming rhino mocks security silverlight sql sql friday sql server sql server 2000 sql server 2005 sql server 2008 sql server 2008 r2 sqlserver structuremap t-sql tip trick unit testing vb.net vista visual studio 2010 windows 7
Authors
- SQLDenis (269)

- chrissie1 (200)

- onpnt (96)

- George Mastros (35)

- Alex Ullrich (24)

- tarwn (16)

- naomi (9)

- ca8msm (7)

- damber (7)

- thatrickguy (7)

- emtucifor (7)

- chopstik (6)

- More...
Main Categories
Search
Google Ads
Tags: nhibernate
Ok so here is how NHProf has helped me solve a problem. This one in particular is a Select N+1 problem which means is that you are executing the same select several times in one session which usualy means you are doing something wrong.
First up the code.
When doing a find all on a class called Fibergroup I get this as a result from NHProf.

Today I noticed that my integration tests with nhibernate were runnning very slow on the build server. Very slow meaning 1 hour to run while they run for 6 minutes on my dev machine all 840 of them. Something was different.
I am using Finalbuilder 5.5 on my build machine and that uses the nunit console to do the dirty work for it.
So I tried running it in the nuint gui tool and there too it was slow.
So I clicked a bit on the tabs, one never knows when one might get lucky and low and behold I was lucky. The Log tab of the GUi builder was getting lots of work.
I ...
I thought it was time to use fluent nhibernate just to keep up. Up untill now I still use the old atributes and nhibernate 1.2.1 because I see no reason to upgrade. It all just works and does what it is supposed to do.
But I don't want to stand in the way of progress and I want to help the VB.Net community ahead. So that Jeremy can feel a bit better about the VB.Net community ;-).
Previous posts can be found here:
Setting up the repositories for our objects is where this really starts to get fun for m...
Previous posts can be found here:
In part two we set up our domain model. Now, before we can test nhibernate’s ability to work with and persist objects, we need to ensure that we’ve defined our schema well enough that NHibernate can create the Schema for us (since t...
:: Next >>


LTD Social Sitings
Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.