What create delay in packet switching?
920749
The main delay in switching is caused by the switch waiting for the entire packet before sending it out. This is called "Store and Forward". This can be alleviated by setting the switch to use "Cut-Through" switching. Cut-Through may go by other names, such as Fast Forwarding. Usually this is only available on higher end (enterprise class) switches. Switching delay will only ever be a problem if you have MANY switches cascaded together. In a typical environment it is really quite negligable.\n\nWhere you will typically see delay in when dealing with a WAN. There are several types of delay there. \n\n1. Serialization Delay: This delay is inversely proportional to the link speed. It is the amount of time it takes to place the bits on the trasmission medium. On a 10 kbit link it takes 0.1 sec to place 1k of data on the link. on 1 10 Mbit link, it would tak 0.0001 sec to place the same 1k\n\n2. Propegation Delay: This delay is caused by the fact that nothing happens instantaniously. In any transmission medium it takes time to go from point A to point B. For copper (and fiber) the speed is 2/3 C (speed of light). For wireless or satellite the speed is C. \n\n3. Queing Delay: This delay is caused by how long it takes for the router to process the incoming data packet against its various rules and whatnot. Unlike the previous two delays, this one is totally controlable.\n\nI am certain there is one more, but my book is at work.\n\nA good resource for delay is Cisco's QoS book. QoS, by definition, is the management of delay.
252853
Occasional network slowness is common, by which I mean a period of slowness that happens maybe 2-3 times a week for a half-hour or less.\n\nIf you're slow all the time -- for more than a half-hour, or every day, especially if it's not always at the same time of day -- it would be something to worry about.\n\nIf you want to try to clear chronic network slowdowns:\n\n1. Shut down the PC.\n2. Turn off the router / switch / hub, if you have one.\n3. Turn off the DSL modem.\n4. Wait a few minutes (3 or 4 minutes).\n5. Turn on the DSL modem and wait for the power light to stop flashing. Ensure the power, data and connection lights are all showing normal (your DSL modem manual will explain what these lights should look like in normal operation).\n6. Turn on the router / switch / hub, if you have one. Make sure its status lights show ready and normal operation; again, check your user manual.\n7. Power up the computer and give it time to go through all the startup files (generally, 2-3 minutes after you see the desktop).\n\nYou should have better performance.
649239
The loop was detected because the packets where leaving one port on the switch and coming back in on another.  If you are going to connect switches together, you have some options.  I dont recommend that you daisy chain because you will more than likely cause a bottleneck on cable that runs from switch to switch.  If the switch does not allow for them to be connected by the backplane (special connections in the back of the switch) then I would connected in hub and spoke model (like a tree).  You start with a root switch and plug the three switches into the root switch, one in each port.  As the root switch's ports are filled up, then you move down to the next layer and continue the same process.  Some switches allow for trunking so that you can actually combine several ports to create one "virtual" trunk line to carry the data.  That way you dont bottleneck on the port.\n\nMake sure you can turn on the Spanning Tree Protocol so that if you create a loop the future, the switch can automatically shut down one of the ports.  This is to prevent you network from comming down in the event of a loop.
123374
Available data rates for Frame relay are commonly up to 4 Mbps, with some providers offering even higher rates.\nIt is a much simpler protocol that works at the data link layer Frame Relay implements no error or flow control. The simplified handling of frames leads to reduced latency, and measures taken to avoid frame build-up at intermediate switches help reduce jitter.
983355
Couple of possibilities, bad NIC, bad patch cable, or bad router. \n\nPacket loss most often occurs believe or not from a bad patch cable.
1109730
well if you are able to choose the transport protocol TCP will resend packets if one is dropped it also makes a connection where udp does neither of these mostly used for DNS lookups and streaming video and stuff
724442
you can use tcp optimizer ?\n\nhttp://www.speedguide.net/downloads.php
263820
This is the data transfer capacity of your switch per second, and usually translates to 1 gigabit of data a second for each port.  That's the optimum data rate, of course.  If you have clients attached to the switch that are 10 or 100 megabits, then they will go at that rate.
902122
Have you done a traceroute to find out where the latency is coming from?\n\nOpen a command prompt and type:\n\ntracert yahoo.com\n\nThis should answer your question.
400951
For several reasons, among them:\n\n1. Your line may be noisy, causing several frames to be re-transmitted.\n2. Other traffic may be competing for bandwidth (either from your computer, or another, if you share the connection).\n3. The modem at the other end of the connection may be rated slower.\n4. Hardware problems, such as a bad cable or connector.
640656
Why don't you do your own homework?  This is clearly a question that was written by a teacher.  Besides, you have already asked a TCP/IP question a few minutes ago.
116354
http://www.networkphysics.com/products/literature/case_studies/mpls.shtml
42555
First you need to know th differnce. To understand the difference between a router and a switch you need to understand the ISO model.\n\nISO/OSI Network Model\nThe standard model for networking protocols and distributed applications is the International Standard Organization's Open System Interconnect (ISO/OSI) model. It defines seven network layers. \n\nLayer 1 - Physical \nPhysical layer defines the cable or physical medium itself, e.g., thinnet, thicknet, unshielded twisted pairs (UTP). All media are functionally equivalent. The main difference is in convenience and cost of installation and maintenance. Converters from one media to another operate at this level. \n\nLayer 2 - Data Link \nData Link layer defines the format of data on the network. A network data frame, aka packet, includes checksum, source and destination address, and data. The largest packet that can be sent through a data link layer defines the Maximum Transmission Unit (MTU). The data link layer handles the physical and logical connections to the packet's destination, using a network interface. A host connected to an Ethernet would have an Ethernet interface to handle connections to the outside world, and a loopback interface to send packets to itself. \n\nEthernet addresses a host using a unique, 48-bit address called its Ethernet address or Media Access Control (MAC) address. MAC addresses are usually represented as six colon-separated pairs of hex digits, e.g., 8:0:20:11:ac:85. This number is unique and is associated with a particular Ethernet device. Hosts with multiple network interfaces should use the same MAC address on each. The data link layer's protocol-specific header specifies the MAC address of the packet's source and destination. When a packet is sent to all hosts (broadcast), a special MAC address (ff:ff:ff:ff:ff:ff) is used. \n\nLayer 3 - Network \nNFS uses Internetwork Protocol (IP) as its network layer interface. IP is responsible for routing, directing datagrams from one network to another. The network layer may have to break large datagrams, larger than MTU, into smaller packets and host receiving the packet will have to reassemble the fragmented datagram. The Internetwork Protocol identifies each host with a 32-bit IP address. IP addresses are written as four dot-separated decimal numbers between 0 and 255, e.g., 129.79.16.40. The leading 1-3 bytes of the IP identify the network and the remaining bytes identifies the host on that network. The network portion of the IP is assigned by InterNIC Registration Services, under the contract to the National Science Foundation, and the host portion of the IP is assigned by the local network administrators, locally by noc@indiana.edu. For large sites, usually subnetted like ours, the first two bytes represents the network portion of the IP, and the third and fourth bytes identify the subnet and host respectively. \n\nEven though IP packets are addressed using IP addresses, hardware addresses must be used to actually transport data from one host to another. The Address Resolution Protocol (ARP) is used to map the IP address to it hardware address. \n\nLayer 4 - Transport \nTransport layer subdivides user-buffer into network-buffer sized datagrams and enforces desired transmission control. Two transport protocols, Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), sits at the transport layer. Reliability and speed are the primary difference between these two protocols. TCP establishes connections between two hosts on the network through 'sockets' which are determined by the IP address and port number. TCP keeps track of the packet delivery order and the packets that must be resent. Maintaining this information for each connection makes TCP a stateful protocol. UDP on the other hand provides a low overhead transmission service, but with less error checking. NFS is built on top of UDP because of its speed and statelessness. Statelessness simplifies the crash
79341
I notice it with two computers, but only when two of us are downloading things at exactly the same time.  It doesn't happen too often.  And I have a 300k connection.  A DS1 would help (1.544Mbps).  A DS3 would fix the problem (45Mbps).
984330
maybe if you got also a 10/100 faster switch to add to your router it might boost the speed enough....i have a linksys router and have not noticed much of a drop in speed
1039801
your network proxy server settings are in default mode, and the packet transfer protocol in bilaspe. correcting these issues will help you find the correct forum or at least catagory for your question,,,,which was what exactly?
326221
A Ethernet hub looks logically identical to an Ethernet bus, and all traffic is visible to all connected interfaces. Therefore, packet collisions are possible, causing serious performance degradation on a busy network.\n\nA switch switches packets to and from connected interfaces by learning the MAC address of each connected host. Therefore, collisions no longer occur between connected hosts which enhances throughput. Also, traffic is not visible between connected hosts; each host sees only traffic "switched" to its interface. Therefore, security is enhanced as well.\n\nA switch is not a router, but modern switches usually recognize VLANs (virtual LANs) allowing several LANs to share a switch.