3 ms·
I thought the irony of that was the masses of RAM that the .NET runtime consumes? Or am I missing that? Every time I opened Management Studio for SQL Server 20
by 72deluxe 13y ago
I thought the irony of that was the masses of RAM that the .NET runtime consumes? Or am I missing that?
Every time I opened Management Studio for SQL Server 2005+, it took forever and caused massive disk churning, compared to the Win32 version for SQL Server 2000 and before, which didn't engage in abstract disk churn and memory gobbling.
- bad_user 13y agoIs that really a function of the app being written on top of .NET? It could be, but most often than not, that's due to poor architectural decisions. Pointing fingers without knowing the internal details isn't constructive criticism.
- tanzam75 13y ago.NET applications should not just churn at random. There needs to be real memory pressure (was there?). I wonder if something went wrong with the native image generation during setup? It may be trying to JIT it every time on startup. That could be quite slow and result in a lot of disk activity.
- kyberias 13y agoIs Management Studio 2005+ written on .NET? Any reference on that?
- 72deluxe 13y agoAs far as I new it was. You noticed the flickering views and new-style GUI controls, eg. looking at the properties of a server caused massive update flicker, common to .NET controls (early versions only?)