01-10-2015, 02:05 PM
I have the same problem, database is small, only 137mb - contains about ~4-5000 server entries. I have done a log cleanup in 2012 before I migrated it to 2015. (got conversion problem during migration)
I have done some statistics for 2012 compared to 2015. The values are from the point when the base program have been started - when I press enter to use the SQL connection, to the point when everything is loaded, and the application is no longer processing any data.
The values have been measured with process explorer.
On SQL Level the CPU usage is almost the same, 3.2 Sec CPU time on 2012 vs 3.7 sec on 2015
The big difference is in the program itself.
In 2012 it required 10.3 sec CPU time and 26.3mb disk read time to startup the application.
in 2015 it took more than 5,5 Minute!! to finish, and 30.6mb on disk side.
The only thing what I saw with process explorer - under threads, that it run this procedure:
clr.dll!GetMetaDataInternalInterfaceFromPublicx0x1b03b
for 5 minutes.
So the difference is significant.
I have done some statistics for 2012 compared to 2015. The values are from the point when the base program have been started - when I press enter to use the SQL connection, to the point when everything is loaded, and the application is no longer processing any data.
The values have been measured with process explorer.
On SQL Level the CPU usage is almost the same, 3.2 Sec CPU time on 2012 vs 3.7 sec on 2015
The big difference is in the program itself.
In 2012 it required 10.3 sec CPU time and 26.3mb disk read time to startup the application.
in 2015 it took more than 5,5 Minute!! to finish, and 30.6mb on disk side.
The only thing what I saw with process explorer - under threads, that it run this procedure:
clr.dll!GetMetaDataInternalInterfaceFromPublicx0x1b03b
for 5 minutes.
So the difference is significant.