.NET 1.1 application performance in Windows 2003 Server
-
Hi Friends, I developed a desktop applcation in .NET 1.1 frameework using C#. The application works perfect in Windows XP or Windows 2000 Server environment, but in Windows 2003 server the application is really slow. The performance is degraded upto 200%. i.e. it takes 4 times more time in Windows 2003 server than under Windows XP or Windows 2000 server. Can anyone tell me what is the problem and can it be rectified. Thanks,
Sushant Duggal.
-
Hi Friends, I developed a desktop applcation in .NET 1.1 frameework using C#. The application works perfect in Windows XP or Windows 2000 Server environment, but in Windows 2003 server the application is really slow. The performance is degraded upto 200%. i.e. it takes 4 times more time in Windows 2003 server than under Windows XP or Windows 2000 server. Can anyone tell me what is the problem and can it be rectified. Thanks,
Sushant Duggal.
Sushant Duggal wrote:
Can anyone tell me what is the problem
Nope. We don't know anything about your code or what your app is doing. If you give us some details, we might be able to suggest something.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
Sushant Duggal wrote:
Can anyone tell me what is the problem
Nope. We don't know anything about your code or what your app is doing. If you give us some details, we might be able to suggest something.
Dave Kreskowiak Microsoft MVP - Visual Basic
Hi Dave, My application is a mail sending application using cdosys.dll. i have used threading concepts to enhance the performance of the application. but the performance is so bad in win2003 server Regards,
Sushant Duggal.
-
Hi Dave, My application is a mail sending application using cdosys.dll. i have used threading concepts to enhance the performance of the application. but the performance is so bad in win2003 server Regards,
Sushant Duggal.
This doesn't help much. You'll have to profile your code on the Server to see where the problem is.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
This doesn't help much. You'll have to profile your code on the Server to see where the problem is.
Dave Kreskowiak Microsoft MVP - Visual Basic
This doesn't help much. You'll have to
profile your code
on the Server to see where the problem is. Hi, Can you tell me what do you mean by profiling the code??? Thanks,
Sushant Duggal.
-
This doesn't help much. You'll have to
profile your code
on the Server to see where the problem is. Hi, Can you tell me what do you mean by profiling the code??? Thanks,
Sushant Duggal.
-
Hi Friends, I developed a desktop applcation in .NET 1.1 frameework using C#. The application works perfect in Windows XP or Windows 2000 Server environment, but in Windows 2003 server the application is really slow. The performance is degraded upto 200%. i.e. it takes 4 times more time in Windows 2003 server than under Windows XP or Windows 2000 server. Can anyone tell me what is the problem and can it be rectified. Thanks,
Sushant Duggal.
Hi, check if the server is ok. I once had a similar situations and begun profiling my application. After several days a figured out that the hard disk was slow because of a badly configured raid system. It could have saved me several days if I just had called our admin to tell him to fix the raid. Robert
-
Hi, check if the server is ok. I once had a similar situations and begun profiling my application. After several days a figured out that the hard disk was slow because of a badly configured raid system. It could have saved me several days if I just had called our admin to tell him to fix the raid. Robert
Thanks Robert, But I tried it on two systems, ans I faced the same problem.:( Can you tell me about profiling. Regards,
Sushant Duggal.
-
Thanks Robert, But I tried it on two systems, ans I faced the same problem.:( Can you tell me about profiling. Regards,
Sushant Duggal.
Hi, in short: 1. Compile your app in Debug mode and put it onto the server. 2. Download and install a profiler on the server (NProf[^] is a free one). 3. Start NProf, select your application and make a test run. 4. In case of NProf the application must shut down before it shows any results. 5. Analyse the results to find which part of your app is slow. Robert