Server Hardware

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

9 hours 41 minutes
Video Transcription
I welcome to modulate. This is less than 8.1 server hardware in modulate. We're discussing sequel authorizations, so we're gonna start at ground zero, which is the server hardware, but we're not going to go too deep into hardware. It does, however, need to be on your mind so that you can more easily identify it
as a possible culprit if you run into unexplained performance problems,
because slow hardware does cause slow performance in a lot of cases.
So in this lesson, we're gonna discuss the three main components that I find to be the most common culprits in slow performing hardware related to hardware configuration.
Now, with that said, let's start at the top.
First, we have the CPU or the central processing unit, sometimes called the brain of the computer
and general. In today's world, the more threads or cores you have, the better your performance will be related to the CPU,
and this is just because it allows the computer to do more things in parallel.
Now it's easy to check performance. You can go to a site such as CPU benchmark, dot net and enter the CPU model that you have. Look at its score and then compare it to other seep use in the same class and see what their scores are.
If, for example, you look at your CPU score and you see that it has a score of 5000
and you look at other steep use there out in the market and you see that they have a score of 35,000
that could be a sign that you need to switch your CPU out with a faster CPU. This because it would appear that you are lagging far behind the other CP use on the market.
So that is one way to check your CPU performance is just go to the benchmark site. Look up your model Compared to other models,
the next component we need to discuss is RAM or random access memory.
Small applications generally need 1 to 2 gigs of RAM. Large applications come rang from 16 gigs to 32 gigs. Maybe more depends with the applications purposes and what it's doing. For example, if you're running a virtualization server, you're typically going to need a lot of RAM to run all those virtual machines.
If you're developing a Web app
for use. But for 10 people at the office, you probably can get away with 1 to 2 gigs of RAM.
So what happens when you run out of RAM? While the operating system will typically start to write memory to the hard drive and the hard drive is much slower than the ram, so you see a huge performance drop. When this happens, the computers will typically still function. Still finish their tasks. It just runs much slower.
In fact, ramps main purpose is to avoid this problem. We technically could build a computer
with the architecture that excluded. RAM and Onley used the hard drive, and it would just be very, very slow compared to other computers, because the hard drives are slower than the ram, and that brings us to our next bullet point. The hard drive now, hard drives have evolved in recent years.
They used to be spend rate drives, which was a spindle sitting over a platter and depending on how fast at platter spun,
that affected how fast your computer could read or write data. In fact, back in my computer repair days, I would have friends give me a laptop and asked why it was so slow and often times the culprit would be a 54 100 rpm hard drive,
and the individual typically respond with. Well, sometimes it's fast, and I would tell them well, as soon as it loads everything into RAM. It is fast, but any time I need to go back into that hard drive, you're going to get that slowdown. And the answer, of course, to them was to, well, get a faster, hard drive.
So there's different speeds. The most common speeds are 5400 70 7200 and 10,000.
And then there's the much faster variation, which is the SST, which stands for solid state drive. The reason the solid state drive is so fast is it has no moving parts. It's simply a solid state. It doesn't move, and its configuration allows it to be much, much more quicker than a
spindle with a rotating platter.
In fact, ah, lot of benchmarks have them at average up to 20 times faster.
So if you find yourself in a scenario where you're trying to choose between a spinning drive or a solid state drive, do try to get that solid state drive because that speed increase is very significant and very noticeable.
So in this lesson we discussed the CPU, the RAM and the hard drive. And those are the three big components that are the most common culprits for slowdown on computer hardware.
So when should you consider computer hardware? Well, when you have unexplained slowdown, you've written good code, you know it's good code. It's just not executing fast. Check your hardware configuration
now. The next bullet point kind of goes in goes hand in hand with the previous one, which is You do not know the hardware server that that's running. You don't know what the hardware is that your server is running on, and this can happen in companies when you make a request for a server of some type and the administrator gives you one,
and you never asked what it's Ah, configuration ist
sometimes not all the time, but sometimes an administrator will I want to say accidentally, maybe give you ah server configuration. That's much slower than what you need. So it's worth looking into,
and the other reason to consider hardware is recent exponential growth of applications, user base or record tracking. If you had hundreds of users before, and now you have thousands of users. Well, you might need to look at that harbor configuration and see if that might be slowing things down a bit.
And that brings us to the 8.1 summary
and this lesson. We discussed the big three components to check related to hardware and poor performance. Thes three components included the CPU, the hard drive and the Ram.
Now, other possibilities do exist. But these are the Big Three that most often end up being the culprit.
Also, new benchmarks sites mean you do not have to be an expert to gauge performance.
You can simply compare scores to those in a similar class. For example, he could compare soup use within the last few years to identify with her. Now you need a new CPU
that brings this lesson to a close, and I hope to see you in the next Thank you. Bye.
Up Next