netwyman

If you're employing a Linux server, you're probably at home with the term load average/system load. By time to time measuring of the load average is helpful to understanding how your servers are performing; if overloaded, Whenever you would like to kill or optimize the processes which consumes higher amount of resource, or provide more and more resources to balance the workload. But how does one determine if your server has sufficient load capacity, and when do you have to be worried? Let's dive in and see. What is a load average? The load average is that the average system load on a Linux server for an outlined period of your time. In other words, it's the CPU demand of a server that features sum of the running and therefore the waiting threads. Typically, the highest or the uptime command will provide the load average of your server with output that appears like: These numbers are the averages of the system load over a period of 1, five, and quarter-hour. Before step...

  Whether it’s a server, or a PC for work, what usually limits performances is disk speed. Even if using SSDs, their speed is not yet comparable to that of RAM and CPU. There are different tools with or without a graphical interface, written for testing disks speed. There are also people who use dd , for example: dd if=/dev/zero of=test_file bs=64k count=16k conv=fdatasync However, in our opinion dd is the worst software for benchmarking I/O performance. it is a single-threaded, sequential-write test. Of course, if running a web server, services do not do long-running sequential writes, and use more than one thread it writes a small amount of data, so the result can be influenced by caching or by RAID’s controller it executes for just a few seconds, and everyone knows that in this way it’s not possible to have consistent results there are no reading speed tests All these points just lead to one conclusion: better to use anything else. For disk benchmarking there are two kind of pa...