Hosting web site on Windows Server 2012 seems slow

Question

0.00/5 (No votes)

See more:

, +

One of my client hosted their web site on a Xeon E5-2640 v2 @ 2.00GHz Server with 32GB Ram, mostly accessed by 30-40 users at the same time. There are no images or videos on the page either, so I'm wondering why is it so slow to load the page? The page mainly consists only text, but with quite a lot of stored procedure working in the database.

And what i noticed is that some of my other client hosted the same site using Desktop PC with i7 processor and 8-16GB of ram, and they all ran faster compared to the above scenario. Do I need to specifically optimize the code in order to work properly on the server?

Posted 22-Jul-15 15:28pm

Member 10217451

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2015-07-22T15:51:00

No, you need to do some analysis of the traffic to find where the bottleneck is.

I take it the production database server and the web server are two different machines.

Follow the traffic starting with the inbound request from the browser. Use a network sniffer to get timings of when the request comes in and when the response goes out. This is the window of time that you have to account for, every millisecond.

Follow the traffic from the web app to the database and back. When does the browser request start? How many queries are generated by that request? How long until the first query is sent to the database? How long until the last query is sent? How long does that take to process? How long until the database response starts? How much data is coming back from the database? Does the web app need all of that data to do its job for the request? How long until the last byte of the database response is sent? How long does the page take to process all this data?

There's a lot of work to do and various sniffers and profilers are going to be required to narrow it down.