How to improve Windows Server 2008 R2 to handle many connections?
Posted
by
invisal
on Server Fault
See other posts from Server Fault
or by invisal
Published on 2013-10-30T03:27:30Z
Indexed on
2013/10/30
3:57 UTC
Read the original article
Hit count: 529
It has been a few days so far that I am trying to figure how to solve this problem. First of all, I am running a website with an average daily page view of 350,000. Previously, all ads management (tracking click and impression that each ads has served) and content were served in a single server with the following spec:
Server 1 OS: Windows 2008 R2 64-Bit CPU: Intel® Core™ i5 - 4 cores RAM: 8 GB Storage: 2 x 1 TB hard drives Bandwidth: 10 TB per month
To improve our website speed, I decided to separate the ads management script to another dedicated server because we have more than 15 advertisers to 30 advertisers per each page.
Server 2 OS: Windows 2008 R2 64-Bit CPU: Intel® Core™ i5 - 4 cores RAM: 4 GB Storage: 2 x 300 GB hard drives Bandwidth: 10 TB per month
The Problem
The problem is that Server 1
can handle both content and ads system. Now, that I take away the ads system and put it at Server 2
. Server 2
can barely serve only ads system.
Test
- First of all, I moved 75% of the ads to
Server 2
. And then, perform a ping to server:ping -t xxxxx
. [I did the ping for 10 minutes and its following similar pattern as below]
Reply from xxxxx bytes=32 time=290ms TTL=116 Reply from xxxxx bytes=32 time=289ms TTL=116 Reply from xxxxx bytes=32 time=320ms TTL=116 Reply from xxxxx bytes=32 time=286ms TTL=116 Reply from xxxxx bytes=32 time=286ms TTL=116 Reply from xxxxx bytes=32 time=348ms TTL=116 Reply from xxxxx bytes=32 time=284ms TTL=116
- Then, I moved 100% of the ads to
Server 2
. Then, perform a ping to server again. [I did the ping for 10 minutes and its following similar pattern as below]
Reply from xxxxx bytes=32 time=290ms TTL=116 Request timed out Reply from xxxxx bytes=32 time=320ms TTL=116 Reply from xxxxx bytes=32 time=286ms TTL=116 Request timed out Request timed out Reply from xxxxx bytes=32 time=284ms TTL=116
Attempts
- Increase
MaxUserPort
andTcpNumConnection
- Restart the server
- Increase IIS
Max Instances
andInstance MaxRequests
Server Resource
- Only 10%-15% of the network connection is used
- Only 10%-15% of the CPU is used
- Only 25% of the memory is used
© Server Fault or respective owner