speed-killers in the network

[promann]

There is the belief that if you have many application users in the network on one side of a router and the application server on the other side of the router, network traffic will be slow. To what extent is this true? Say, for example: PCs-HUB/PATCHPANEL-ROUTER-SWITCH-SERVER sequence.
How would this sequence affect network speed, all other things being equal? So, does it matter how you use patch-panels, routers, switches in a sequence, that is, between users on PCs and the server(s) - in terms of overall network speed? If it does matter, why and how?
It would be nice to hear from someone who has actually taken some measurements, as well. Thanks.

[spaceAlien]

Read you post several times -- I can't quite figure out what you're asking.

Every piece of hardware has a bandwidth, or throughput. If you get enough traffic, then you will have congestion. The more pieces you have to go through, the more likelyhood of a bottleneck.

If you're asking about network topology, then we need some very specific information about hardware, number of users, geography, etc.

If you have a router connecting two subnets, then there is probably a reason the router is there. The usual reason is geography - the subnets are in different places. If the hubs, router, switch and server are in the same room, then for some reason, somebody wanted to separate the traffic of the server from that of the users. If most of the server traffic is going to the users, and most of the user traffic is going to the server, then it would make sense to have them on the same side of the router -- if they are geographically close.

All for now --




------------------
HEY YOU -- MODERATOR -- CHANGE MY STATUS TO "HECKLER"

[Ghost_Hacker]

Networking 101--- Always try to place resources close to the users who need them.

Now first take the patch panel out of the discussion. It has no bearing on network speed. A good network installation ,including the patch panel, can improve bandwidth percentage by providing a good channel, but once it's in place that's it.

Second ask yourself. Do you need both a router and a switch? These 2 devices are the key to improving your network design and ,unless your working with vlans or doing some heavy subnetting, you don't need both. (mabey a switch to switch setup would be better.)


If you do need all the devices you have listed there isn't much you could do ( all things being equal) to improve speed other than replace the hub or router with a switch. The hub is your biggest bottle neck since it supports only half-dublex operations and all devices connected to it share that segment's bandwidth. The router on the other hand must read the IP header of each packet sent to it and then access it's route tables before passing a packet out one of it's interfaces. This can be a slow process because it's software driven, so a good rule to follow is "switch when you can, route if you must."


Hope this helps http://www.PCGuide.com/ubb/smile.gif

------------------
Comment heard from a Klingon programmer.

"Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!"



[This message has been edited by Ghost_Hacker (edited 07-13-2001).]

[promann]

Thanks to Ghost_Hacker and SpaceAlien for your useful contributions. The Network 101 idea is great. It appears though that many people have different ideas about what is efficient and effective in a network. Since not everybody will read this Forum, there's no end to network crashes! http://www.PCGuide.com/ubb/smile.gif

------------------
IF u Seek, U'll Find