Hibernate version:
1.0.2.0 just upgraded was running 1.0.0.0

Code between sessionFactory.openSession() and session.close():
I have implemented the following technique to handle the session

http://blogs.intesoft.net/simon/articles/16.aspx


I have an asp.net appliction. Everything I do causes the sqlservr to eat more and more memory. It never goes down just up. Every single db oriented request consumes more memory and its never released.

Can somone point me in the right direction on troubleshooting this.

Thanks

Sean

From my experience, this is common behavior for SQL Server, as it rearly (if ever) releases memory/ This is by design, in fact it keeps the allocated memory as pool. I've seen this even in an article or Book online, I don't remember for sure...

Dragos

Can you all let me know what kind of memory consumption you see when running through an asp.net app using nhibernate. I see ~500kb get consumed just moving from one page to the next. This seems like alot?

Maybe Im doing something drastically wrong? When you work in asp.net do you serialize objects between one page to the next? Or do you request them again from the nh cache?


Thanks

Sean

Ok, I feel kinda dumb...What I found was that the horrible performance and high memory consumption was being caused by the amount of logging I was doing.... I had the log4net set to 'debug' and in many cases 8500 rows were getting written for a transaction. I cut the logging level back to 'warn' and I was back to sub second querys.

I am still curious...As to how everyone handles object in a stateless environment?

When you work in asp.net do you serialize objects between one page to the next? Or do you request them again from the nh cache?

Thanks to everyone for their feedback and to the development team for their hard work.

Sean