3 ms·
Is 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 fi
by bad_user 13y ago
Is 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.