2nd nic ?

  • Thread starter Thread starter FasiFreak
  • Start date Start date
F

FasiFreak

Well i have a webserver that is hosted on my LAN with role to provide users
(200) with large (mpg) media files ..
during rush hour my webserver (win2003 web edition with IIS6) becomes to
slow to acess & file downloading become to slow i was thinking should i add
another NIC on the same system help in improving the performance ?
 
Check task manager during a slowdown to see if the bottleneck is CPU or
memory. You may want to use Perfmon to determine exactly what is happening.
My guess is that you should add more RAM.

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
My processor is 750mhz .. & ram is 512MB ... i checked & it seems that there
is no extra ordinally processor activity nor there is any memory shortage ..

can it be HDD issue 2 ?
i have IDE HDD's with 7200 rpm speed ...
 
FasiFreak said:
Well i have a webserver that is hosted on my LAN with role to provide users
(200) with large (mpg) media files ..
during rush hour my webserver (win2003 web edition with IIS6) becomes to
slow to acess & file downloading become to slow i was thinking should i add
another NIC on the same system help in improving the performance ?
Click to expand...

Not enough information to determine if the bottleneck is disk, network.
or memory. I would suspect that it is disk, but you didn't say
if you are running 10/100/1000, if you are partitioning your network
into many small collision domains, or what.

Use Perfmon and check Physical Disk -> current disk queue length for the
disk containing the mpg files. If this is greater than .15 x to 2x the
number of spindles you have, disk is the bottleneck. Adding memory for
cache might be your best bet. Using RAID and disks rated 15,000 rpm is
another step. You have to run Diskperf -y prior to sampling disk
performance.

For network performance, with perfmon, check Server -> Bytes Total/Sec
If the server is not in its own collision domain 40% usage on Ethernet
is considered OK, much more usage and the network gets bogged down
by the collisions. Network Monitor, a 3rd party app or just checking the
lights on the card can be used to check for excessive collisions on
the segment.

If it is network performance and the server is plugged directly into a switch,
a second NIC card would be a good idea. If you see a lot of collisions,
give the server its own port on the switch (or get a switch if you don't
have one). Also check to see if your NIC card is up to the task or if
you can get a high performance replacement.

--
Matt Hickman
With fast ice, little air resistance, and the low Martian
gravity the speed of a skater on Mars is limited by his
skill in stroking.
- Robert A. Heinlein (1907-1988)
_Red Planet_ c. 1949
 
Back
Top