On Sat, 2009-06-13 at 22:07 +0300, Andrus Moor wrote:
> I have some hundres of tables in a DbMetal generated DataContext class with
> a lot of foreign key relations.
>
> Using DbLinq from SVN causes test below to take 5 seconds to run and CPU
> usage is 100%.
> In old DbLinq this test will complete immediately. This makes new DbLinq
> useless for me.
Oof. I'm sorry to hear that.
Alas, all I can currently suggest is one of two things:
1. Use a profiler. I hear good things about dotTrace (though I've never
used it).
2. Add some `Console.WriteLine("{0} Description Here", DateTime.Now);`
lines to the DataContext constructor and related methods (e.g. Init())
and narrow down which method is responsible for the overhead. (AKA,
manually do what a good profiler should do for you, but at least it's
free!)
Alas, lacking additional information and/or a reproducible test case,
there's not much I can do.
Though given your other message, it looks like you've narrowed it down
to AttributeMappingSource. Perhaps the real solution is to make
AttributeMappingSource lazy?
- Jon
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
