2009/6/17 Andrus Moor <[email protected]> > > > Step 1 is lines 3-4, taking 348820 ticks. > > Unlike others, step 1 is speed probably exponentially depends from the > number of tables in DataContext class: > > If DataContext contains 2 times more tables, number of relations (class > members) will typically increase 4 times and thus DataContext constructor > speed will decrease also 4 times. >
I'm not sure... First becouse the member has no state by itself, and the constructor have nothing to do with it (AFAIK) Second becouse (with DbLinq only) you could also have entities directly accessed by the GetTable<T>() method. What we could improve in some way would probably be 1. Vendor load and creation 2. that fucking ObjectFactory... :-D Giacomo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" 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/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
