8 Answers, 1 is accepted
Out of interest, is this with VS2010 SP1 installed ?
Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel
Installed Version: Ultimate
With Q1 2011 release, OpenAccess has integration with the Intellitrace debugging mechanism of Visual Studio 2010. It is expected to have lowered performance when this feature is turned on(only in Debug mode though) and here is the help article that shows you how to fully utilize Intellitrace into debugging OpenAccess based applications.
Greetings,Zoran
the Telerik team
From the documentation article:
>> Using the default settings, IntelliTrace has little effect on performance.
and then you added in your reply:
>> It is expected to have lowered performance when this feature is turned on
In our experience we saw our ORM slowed down by a factor of 30X, so a page that previously spent .5 seconds in ORM queries was taking 15+ seconds afterwards. I don't think this can be characterized as "little effect on performance". For example, I would restate the documentation to say, "Using the default settings, Intellitrace can have a dramatic effect on performance, in some cases slowing down queries so they take 20X-30X longer to execute."
In addition, I would suggest that you have the ORM intellitrace integration disabled by default. I would assert the majority of users will not use Intellitrace most of the time. Those that are troubleshooting performance issues could easily go enable it when they need it.
In addition this could have negative consequences for Telerik, since if OpenAccess is being evaluated/compared side-by-side with other ORMs and the slowdown is observed, OpenAccess would be unfairly eliminated due to slow performance.
Actually, the sentence is there in the documentation because the default settings are to have the intellitrace integration disabled. I am not sure what was the reason that you had it otherwise on your side, are you sure that it was turned on by default when you just installed OpenAccess. If this is true than this means that there is a problem on our side, maybe with the default settings that we install with the product. However this is an issue we have not observed yet, while testing the product on our side.
Greetings,Zoran
the Telerik team
Thanks
This problem with IntelliTrace and ORM queries being REAL SLOW has returned with Q2 2015 Data Access. If IntelliTrace is on while debugging queries against the DB take an order of magnitude longer to execute. If I have IntelliTrace off or I am not debugging, the queries are fast again.
Help!
Also, consider restricting the types of events that get traced to limit the performance impact.
Regards,
Thomas
Telerik