Hi, I’m using nhibernate in a very big project and I have the following problem, when I execute the application, in de main form I’m getting a new session (OpenSession()) and it’s taking a lot of time.
Anybody has any suggestion to improve performance?

Thanks Martin

if this happens only on application startup, try



in your configuration.

Regards
Klaus

Klaus, it works really well.
Thank you very much for your reply.

Do you know what change that key?
Can you explain me a little bit more about it?

Thanks again, Martin

NHibernate dynamically generates proxy classes to access the getters and setters of your model classes on startup by default to omit the permanent use of reflection. If you have mapped many classes this process will take some time. The advantage is, that the overall performance is a little bit better. The option i told you disables this behavior. NHibernate will access your mapped classes via reflection all the time.

Me and my team are just implementing an application which use a quite big model which contains around 100 classes. We have done some performance tests with and without setting the option and found that the performance penalty is in the range of tenths of a second. So we decided to accept this as the startup time of the application was inaccepatable 1 - 2 Minutes depending on the hardware.

Regards
Klaus

It just occurred to me that it is actually strange that you'd have to generate these classes each time you start the application; they will only differ between different releases of your application.

It would be nice to be able to generate an assembly with these classes upon release of your application, so that the classes just need to be loaded when the user starts the application in stead of re-generating them each time.

Is anybody aware of a reason why this would not be possible? If not, are there plans to support such behavior in future versions of NHibernate?