{"id":180,"date":"2021-02-03T23:01:19","date_gmt":"2021-02-03T23:01:19","guid":{"rendered":"https:\/\/hoganhost.com.ng\/blog\/?p=180"},"modified":"2024-08-12T13:35:54","modified_gmt":"2024-08-12T12:35:54","slug":"how-to-reduce-server-load-average","status":"publish","type":"post","link":"https:\/\/hoganhost.com.ng\/blog\/server\/how-to-reduce-server-load-average\/","title":{"rendered":"How to Reduce Server Load Average"},"content":{"rendered":"

\"\"<\/p>\n

If you work too hard, you’ll eventually get tired, and your productivity will decline. Although computers are capable of working 24\/7, they also slow down when pushed to their limits. Therefore, if your website is sending excessive requests to your server, then the whole system’s performance will surely suffer. This guide will cover some easy ways to\u00a0improve your website’s performance<\/strong>\u00a0by reducing your server load.<\/p>\n

What is server load?<\/h3>\n

When developers use the word “load” as a noun, they are referring to the amount of processes necessary for a computer system to operate. The more CPU and disk space your server requires, the greater its load grows. The “load average” is the average load over a given period of time. Load averages are typically presented as three numbers indicating the load 1 minute ago, five minutes ago and 15 minutes ago respectively.<\/p>\n

Checking the server load<\/h3>\n

How you check your server load may differ slightly from operating system to operating system. In Linux and Unix, one option is to use the uptime command as follows:<\/p>\n

$ uptime\r\n13:40:40 up 38 days, 1:07, 1 user, load average: 0.25, 0.14, 0.14<\/code><\/pre>\n
In the output above, the first figure is the time the command was executed. The next part indicates that the server has been up for 38 days, one hour and 7 minutes, and there is one user logged in. The load averages are at the end. As you can see, load averages can vary drastically from minute to minute, which is why taking multiple measurements is so important.<\/p>\n
Understanding the server load<\/h3>\n
A load of “1” means that a single processor is working at maximum capacity. If your system has two CPUs, then a load of “1” would indicate that your system is using half of the processing power available to it. Consequently, if your server load is greater than the number of CPUs you have, then you should expect problems since some processes are having to wait in a queue.<\/p>\n
Ideally, you want your server load to\u00a0be around 0.7 or less<\/strong>. If you need to check the number of available CPUs, run this command:<\/p>\n
grep processor \/proc\/cpuinfo | wc -l<\/code><\/pre>\n
For real-time information about your server’s resource usage, you can use the\u00a0top<\/code>\u00a0command like so:<\/p>\n
\"\"<\/p>\n
You’ll see a dynamic readout that updates automatically every few seconds. You can sort processes by CPU or memory usage to get a sense of where your server’s resources are being spent. Keep in mind that running the top command requires the use of resources, so it actually inflates your server load by a little bit.<\/p>\n
Tools for monitoring your server load<\/h3>\n
If you’re more of a visual learner, try using\u00a0flame graph tools<\/a>. Flame graphs compile data drawn from multiple profiling tools to produce comprehensive graphical representations of your system’s resource usage. In the example below, the wide rectangles indicate assets that are consuming the most resources.<\/p>\n
\"\"<\/p>\n
How CDNs reduce your server load<\/h3>\n
If you’re not already using a premium\u00a0content delivery network, it might be time to consider the investment. CDNs are distributed networks comprised of strategically placed edge servers that enable the rapid delivery of web content to users across the world. A CDN can reduce your server load and speed up your website by caching your site’s static content.<\/p>\n
By keeping copies of your website stored on points of presence around the globe, a CDN ensures that visitors receive content from a server that is geographically close to them. Thus, round trip time is drastically reduced, and your visitors from afar won’t slow things down for your local users.<\/p>\n
Given that a typical site can be comprised of up to\u00a080% static assets<\/strong>, using a CDN can be a great help in offloading data from your origin server.<\/p>\n
More tips to reduce your server load<\/h3>\n
1. Optimize your images<\/div>\n
Images usually account for more than half of a website’s bandwidth usage, so\u00a0optimizing your image files\u00a0is always a good place to start. Additionally, where possible, use CSS code in place of images.<\/p>\n
2. Compress your CSS<\/div>\n
Speaking of which, you can cut down the size of your CSS files by using\u00a0CSS shorthand properties<\/a>\u00a0or a CSS compressor tool. While you’re at it, get rid of any unnecessary HTML, tags and white space in your markup. Check out this guide for tools and tips on how to\u00a0minify your CSS, JS, and HTML.<\/p>\n
3. Compress your data<\/div>\n
Always use a compression algorithm such as\u00a0Gzip\u00a0or\u00a0Brotli\u00a0to instantly shrink the size of your webpage. While Brotli is still in the process of being globally adopted, KeyCDN is proud to\u00a0fully support Brotli\u00a0to help you in even further accelerating your site’s content.<\/p>\n
4. Host your images elsewhere<\/div>\n
If possible, hosting your images on websites like Flickr or ImageShack is another way to reduce your server load. If an image you need is already hosted on another website, try linking to its location instead of hosting a copy of the file on your own server. If you do host your own images, then you might want to enable\u00a0hotlink protection\u00a0in your image folder to prevent others from slowing down your site and using your resources.<\/p>\n
Summary<\/h3>\n
There are dozens of factors that can drag down a website’s performance. If reducing your server load doesn’t result in your website running more smoothly, then you probably have other problems that need to be addressed. However, if you’ve noticed that your origin server’s load has been peaking and that it’s causing concerns, consider using the tips mentioned above to either reduce or offload data from your origin.<\/p>\n
\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n<\/article>\n
\n
\n
\n
\n
Defining and Improving Website Load Testing<\/h3>\n
Before launching a website, you want to be sure it can handle the expected level of activity without slowing down or crashing. Load testing allows you to see how your site will perform under “real world” conditions and helps you identify\u2026<\/p>\n<\/article>\n
\n
Scalability Testing – A Guide and Checklist<\/h3>\n
You can build a web application that functions perfectly on your machine, yet if it doesn’t scale, a sudden influx of traffic could cripple your whole system. That’s why it’s important to have measures in place that allow your application to quickly\u2026<\/p>\n<\/article>\n
\n
How to Effectively Monitor and Scale for Website Traffic<\/h3>\n
Scaling when it pertains to web performance essentially means the ability to support any traffic load. Unfortunately most business owners don’t think about this until their website goes down due to heavy traffic. That is why it is very important to\u2026<\/p>\n<\/article>\n<\/div>\n<\/div>\n<\/div>\n