For organizations that are monitoring and maintaining a large network, bandwidth consumption can cause major issues. Knowing who is using all the bandwidth in the company is particularly helpful when troubleshooting performance issues and all too common complaints that “the network is slow!” Insight into what external web sites employees are visiting, and whether or not those sites are work-related is important. Today, almost everyone uses the Internet for everything from news updates, to dating, to banking, to music, and so on. Many of these will not consume too much bandwidth, but that depends on the service.
Archive.org generates 75 MB
As you can see there are many instances of Pandora.com, based on the server where the music is playing from. Archive.org seems to work in a similar fashion, however there are fewer servers as the play selection is distributed differently. Archive.org is creating three times the traffic in the hourdisplayed. Seeing that we have a T1 or 1.544 Mb, this means that streaming music was using up one seventh of the overall bandwidth! So, getting a grasp on the streaming of music in the workplace can be helpful to verify the use of a previous resource. If Pandora.com can generate significantly less bandwidth than Archive.org, it may be a good practice to block Archive.org. This is exactly why flow analysis is critical to network monitoring. As companies deploy more performance sensitive applications like VoIP, video, VDI and cloud services, performance really matters. The more bandwidth being utilized by the end user, the less bandwidth is available for work related tasks.