Performance issues with version 3.2.x
Posted: Wed 04 Apr 2012 15:30
I encountered performance problems after upgrading dotConnect for Mysql to versions 6.80.x. (I have tried both 6.80.325 and 6.80.332).
It is apparent on complex linq queries (nested etc.), so it's quite hard to debug.
However, sql generated remains still the same and according to DB monitor it executes still very fast. There is no problem with sql but with constructing queries.
For example, time spent on a query
- with version 6.70.302.0 - Elapsed: 00:00:00.0778889 (Context: Devart.Data.MySql.Linq.Provider.MySqlDataProvider Model: an Build: 3.1.34.0)
- with version 6.80.332.0 - Elapsed: 00:00:02.4041109 (Context: Devart.Data.MySql.Linq.Provider.MySqlDataProvider Model: an Build: 3.2.64.0)
I haven't posted a specific query because it is really very complex. At first, I'd like to ask if there was any fundamental changes in the compilation of queries or in handling of compiled query cache.
Thanks for your attention.
It is apparent on complex linq queries (nested etc.), so it's quite hard to debug.
However, sql generated remains still the same and according to DB monitor it executes still very fast. There is no problem with sql but with constructing queries.
For example, time spent on a query
- with version 6.70.302.0 - Elapsed: 00:00:00.0778889 (Context: Devart.Data.MySql.Linq.Provider.MySqlDataProvider Model: an Build: 3.1.34.0)
- with version 6.80.332.0 - Elapsed: 00:00:02.4041109 (Context: Devart.Data.MySql.Linq.Provider.MySqlDataProvider Model: an Build: 3.2.64.0)
I haven't posted a specific query because it is really very complex. At first, I'd like to ask if there was any fundamental changes in the compilation of queries or in handling of compiled query cache.
Thanks for your attention.