nhprof didn't seem to provide too much insight; the query itself takes 6 seconds or less, generally about 4 on production hardware I believe. The vast majority of time is spent inside of collection initialization, and reading rows from the resultset.
And yes, all records are required -- this is a "get all products" call. could it be partitioned by leading letter of the product name or similar? Sure, but that would require engaging in a red-tape laden, potentially politicized process around interface/contract/client behavior changes. Not entirely sure what result datatables would give me, or how you would envision them fitting in? I'm currently pursuing a view/stored proc ADO.NETsolution, or at least test, where I make a single DB call against a flattened view, then pull out rows by matching product number, then hydrate the objects for each set of rows. This requires iterating each set of rows, but allows me to introduce Parallel.ForEach calls to take greater advantage of multiple core processors when hydrating these objects. --ab On Tue, Apr 19, 2011 at 3:52 PM, Jason Meckley <[email protected]>wrote: > it's probably the volume of data that the problem. do you need all 4000 > entities with all 60 properties at once? as a comparison you can run your NH > queries through NHProf to see how long the query vs hydration takes. you can > also compare what the results are using raw ADO.Net & datatables. I would > bet the numbers are not that much better. > -- 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.
