Next step for you is to get the source code and trace into the QueryBuilder class, where the query is built (hence the name ;)), and tell us why the query doesn't go in the cache (QueryCache class).
On Wed, Nov 19, 2008 at 17:09, Jimbo1982 <[EMAIL PROTECTED]> wrote: > > Hi, > > There is definatily only one DataContext created when I create a > connection to the database on startup. I have nothing eating up my CPU > and everything is very responsive while the application is running > each select, looking at the process explorer the CPU sits around > 20-30% when the app isn't running. > > Any other ideas I would really like to stick with Linq and DBLinq it > is very cool. > > Cheers, > > James > > > -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
