Thanks for the replies. I realized after posting that this was the dev group.
Actually Fabio, the link is mine in the users group :$ Sorry for the wrong posting. Bye and thanks Leonardo On 17 feb, 10:03, Fabio Maulo <[email protected]> wrote: > Please have a look to this long > threadhttp://groups.google.com/group/nhusers/browse_thread/thread/e29fd1f53... > > 2010/2/9 Leonardo Garcia Crespo <[email protected]> > > > > > > > Hi! > > I've seen that Fabio and Ayende a long time ago said that Transactions > > are mandatory, even if only querying. They quoted the Hibernate > > reference also. > > > I've seen all this, as I wasn't aware of this practise, so I decided > > to apply it. But when I did that, I found it's taking a lot of time to > > open a transaction (I have the DB in USA, and my app in dev > > environment is running here, in Argentina, so it has a little round > > trip time to call a begin transaction). > > > A request to a page from my site, without transactions, is lasting > > 400ms, where as with transaction, it lasts 800ms. > > Only a simple Get is inside de transaction, and one lazy property > > being called in the view (that is also inside the transaction). > > > So I started thinking, is this truly a good practise? What am I doing > > wrong by using a transaction in this case? Should I return to using > > transactions only when modifying entities? What are the problems I've > > got if I don't use a transaction when only reading? > > > Thanks for anyone who can answer this! > > > Leonardo > > -- > Fabio Maulo
