What could be the reasons for brakes on asp.net?

Question

IIS

The bottom line is this: the programmer wrote a calculator in C#. Everything worked fine on the local machine. After it was transferred to the server (local), wild brakes appeared (namely, the calculation process).
The programmer quit and is no longer available.
Tell me, in which direction to pick? What could be the problem (hardware, code or server settings)?

Answer 1

You need a profiler. See which builds are running the longest. By and large - without a code, this is a look into a crystal ball