ah... and before think about NH perf you should think in doing the same with pure ADO.NET.
2009/5/23 Fabio Maulo <[email protected]> > for NH2.0.1:1) NH is not the right way to manage massive data manipulation > 2) try statelesssession > 3) if you want use statefull session close or clear it each 500 iteration > (for example) > 4) NH2.1.0 has executable HQL > http://fabiomaulo.blogspot.com/2009/05/nhibernate-210-executable-queries.html > > 2009/5/22 Nelson <[email protected]> > > >> Hi, >> >> My current application heavily relies on NHibernate 2.0.1. I currently >> have a bottleneck, in which my application might insert around 6 000 >> 000 entities (calculations in facts). I currently resolved the problem >> by setting the adonet.bath_size property to 100. >> >> With a batch-size of 100, 36000 entities are inserted in 100 seconds. >> As I am a great mathematician, I have deduced that inserting 6 000 000 >> (6 millions!) entities might take up to 240 minutes (=4 hours). I >> think it is due to the 6 000 000 / 100 = 60 000 queries (slow network >> I guess). >> >> Supposing this is linear time problem, setting the batch size to 1000 >> should divide this time by 10, and to 2000 should make a total time of >> 12 minutes, which would be awesome. But, when setting the batch size >> to 1000 I noticed that insert commands where batched by 100. >> >> My question is then : where does this limit comes from? I can't find >> any answer on google. You are my last hope NHUSER GROUP!! >> >> Have a great weekend ! >> >> >> >> > > > -- > Fabio Maulo > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
