Hi and welcome to Sigh Bury. My name's Anthony and I'm your local subject matter expert for Network Plus And today we're gonna be talking about different methods and rationales for network performance optimization.
So we're talking about optimizing our network. I'm we're talking about the different rationales we have for optimizing our network. What do you mean by that?
Well, we were using different applications were using different service is on our network. Some of the service is not like the others. Not all service is air equal. Not all applications and not all network traffic is equal. So we need to understand the rationales. We need to understand the reasoning behind these different network traffics
and what type of traffic they use and how much data they use
and as well as how sensitive they are to any delay in their communications when we're deciding how we're going to optimize our network for these particular applications for these particular data sources. So one of the reasons that we need thio optimize our network
off applications that are what we call Layton's Leighton see sensitive.
Now wait and see sensitive applications are essentially their data packets that they're more susceptible. They're more affected by a delay in our network communications. This may be a delayed caused by slow, just general slowness of our network made. We don't have a very good Internet connection
and maybe delay caused by
how many users are on our network. How much data were already sending and receiving over our network. Or that may just be delayed. That's caused by older devices that we have routing our network or switching our network. But whatever the case is
those data packets, the
sort of impartial to all of this, they just because our devices can't send them this quickly. Just because we can't receive them as quickly doesn't mean that those packets are going to going to change in order to in order to help us with that. Now
we were talking about our legacy sensitive applications, a lot of seven up data packets that come to mind. Our verse of I P R video are remote desktop remote desktop applications. Essentially, these air applications that we want running in real time. If we're streaming the video, we're up.
We're sending a receiving a video conference call with somebody, and we're trying to talk with them and see on see them and they're trying to hear our voice.
Then we need to have that connection. Be very. We need to have very little Leighton see on that connection. We wanted to go, but we wanted to connect to us very quickly. We want that packet to be one of the first packets that come to us. And one of the most highly prioritized packets were essentially want to make sure that
we get those packets first because they're more sensitive to delay.
We'll talk about how we how we adjust our network through those packets to help make sure that we give them, as we make sure they encounter as little Leighton. CIA's possible. You may may have watched the news before and see, and you've seen when they're talking to other reporters across the country
and you see one reporter talk and ask the other reporter a question
and then tense and five or 10 seconds go by before it seems like the other person is hearing them because of the late and see the amount of time it takes for the signal to get from one side of the country to the other the same exact thing when you're on a say, a VoIP call over the Internet or you're talking over a Skype call or talking over a
Google video call, and
you noticed that the car was coming through kind of choppy. There's a little bit of a delay in the communication. This is because of latent. See, somewhere along the communications between the potion you're trying to talk to and you there's some sort of delay in the packets that need to be needs to be addressed.
So we're gonna talk about some of the methods that we have for optimizing our network
to help with this. Leighton see things like quality of service, but we'll get into that and just in just a little bit
Another one of the rationale is that we have another one of the reasons we have for optimizing our network or in order for us to be able to handle high bandwith applications. Now, hi, Been with applications are a little bit different. See different than Leighton. See sensitive applications because hae been with applications may or may not be late and see sensitive,
but high bandwith applications are
applications are data that are taking up a large portion of our network traffic they're using up. A lot of our resource is now. This may be something that we want happening. We may be a file hosting site. We may be somewhat. We may be a site where we have a lot of remote connections coming into us,
so we may have a lot of high band with traffic,
but we need to know how to pin this traffic down in case it's something we don't want on our site. Maybe we have someone in office who is downloading or 20 a lot of different files while they're at work. Maybe they're hosting or their seeding a lot of different files at work, and this is causing a lot of high band with traffic
on our network. That's taking up on Network. Resource is
that's making the network slower for everyone else, but isn't legitimate work network traffic. So we need to be aware of these high bandwith applications again. Not all applications are created equally. The amount of network traffic that goes on when you connect to your email
isn't the same is the amount of network traffic that goes on when you're streaming ah, high quality HD video.
the applications that use a lot of the network traffic we referred to his high band with applications, and these can be things such as video or music streaming. You may notice that if you have someone on your network that does a lot of, Ah does a lot of high quality music streaming, you'll see a lot of network trump traffic coming from that
they they may be doing file streaming or file hosting from their computer
or even cloud applications. One of the downsides to outsourcing all of your applications and hosting them on the cloud is that when people are trying to connect to those applicant when people try to use those applications from your workforce, say, maybe you use an online hosted
cloud service for your word processing and your email and ah, couple of other of your applications eso maybe some editing applications that you don't want to host in house.
Well, whenever somebody needs to connect to that you're not using local resource is, but one of the resource is you are using locally is your network resource is, and the more of those cloud applications that you implement, the more network traffic you're gonna have to expect from that. So cloud applications a CZ we see cloud as we see hosting applications on the
becoming bigger and bigger. You're gonna notice more and more network traffic from that. So we wanna watch out for these on our network
number one, so that as we noticed the increase in traffic flow, we can begin to possibly expand or look at expanding our network in orderto handle it, but also so if we see a sudden influx of high bandwidth usage from a particular application than we want to try to track down where that's coming from,
so that if it's legitimate that we can adjust our network for it.
But if it's illegitimate, maybe a user abusing our network, we can track that down and we could put a stop to it. So now that we know are now that we know to about rationales are late and see sensitivity as well as our high bandwith applications. Let's go ahead and take a look at some of the methods that we can use
in order to allow our network to better handle these types of requirements.