Did that this morning. Our largest set of data loads in about 30 seconds, which I have been told is pretty good compared to application that we are tasked with replacing. Our smaller sets load in several seconds. Doing this I was able to eliminate all the .Future() queries I had been playing around with.
On Wednesday, April 24, 2013 2:35:24 AM UTC-5, Frédéric Delaporte wrote: > > Just a thought, have you devise and set up as needed batch-size on your > collections for lazy-loading? ( > http://nhforge.org/doc/nh/en/index.html#collections-mapping ) And on your > entities which are mapped as many-to-one ( > http://nhforge.org/doc/nh/en/index.html#mapping-declaration-class ). > If not, you may have n+1 round-trip to DB troubles which could be solved > by those kind of mapping adjustments. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
