SOLVED: Suggestions For Troubleshooting A Slow Linux Server.

If you have a slow linux server troubleshooter, the guide below can help you.

Step One: Update Ubuntu.A few steps: Managing startup applications.Step 3: Find the best mirrors for software updates.Step 4: Enable proprietary drivers.Step 5: Install preload.Step 6: Use apt-fast instead of apt-get.Step 10: Reduce system overheating.


If you’ve dealt with the system administrator long enough, you’ve seen the horrendous “server slow” incidents. Again, for a long time, this kind of injury left a hole in my stomach. How the hell can you fix something so subjective? A typical “slow” user might just be stuck because other processes (including unscheduled ones) are running and consuming more parameters than usual, or they might just be there having a server problem.

When I started working as a solid system administrator, I immediately answered: “I need more information about this.” Well, usually the user can’t provide more information because these people don’t know what’s going on behind the scenes or how to explain what they’re seeing other than “that’s definitely slow”. I am yesI answer the user, the number of things.Login


A Huge Number Of Things You Can Discover By Logging Into A Host. Can You Connect At All? Is The Connection Faulty? Or The ssh Command Already Has Three Levels Of Debugging, Each Providing A Ton Of Information Before You Even Log In. To Enable Debugging, Simply Add The -v Option To v. For Example, A Level 3 Debug That I Could Exclusively Use Would Probably Be:

[~]$ -vvv Ssh

3″ “big” (aka CPU, RAM And Disk I/O)

Now let’s look at the two main causes of server slowdown: CPU, RAM, and disk I/O. CPU usage can lead to an overall slowdown in its host and difficulty in completing existing tasks in a timely manner. Some of the tools I use when analyzing CPU are Andsar top.CPU

Check The Use Of A Fitted Top

The top utility gives you a real-time overview of what’s happening on the server as well. According toThe default start time top shows almost all CPU activity:

This view can be changed by pressing the number key 1, and usually more detailed information about the usage values ​​of each CPU is added:

In this view, you should monitor the load average (displayed on the right side of the top row) and the value of all of the following parameters for each processor:

  • us: This fee is the amount of CPU used by user processes.
  • sy: This percentage indicates the amount of CPU consumed by system processes.
  • id: represents the idle percentage of each processor.
  • linux server slow troubleshooting

    Any of these three values ​​can give you a pretty good real-time indication of whether processors are associated with user handlers or system processes.

    You’ll need your own information to really explain average deliveries. For this reason, in this article I will speak in general terms. The three load averages, from left to right, represent one-minute, five-minutemorning and additional 15-minute averages. Generally speaking, if you find that your one-minute average exceeds the number of associated physical CPUs you have, then the particular system most likely has a CPU hang.

    Note. For more information on Last Everyday and why some people think this number is stupid, check out Brendan Gregg’s detailed research.

    Test All Specific Big Three With Sar

    Why is my server slow?

    The reasons for slow servers are usually web hosting considerations. You may be experiencing a slow website because your site is hosted on a free internet host. You are using low-quality hosting with poor content. Or your site needs a hosting account with enhanced features and big money, such as VPS.

    For historical CPU performance data, I rely on the sar command provided by the sysstat package. Most web versions of Linux have sysstat installed by default, but if it’s safe to do so, you can add it using your distribution’s package manager. The sar application collects system data every 10 hours using a cron job located in /etc/cron.d/sysstat (CentOS 7.6). This is what all the “big three” check with sar.

    Note. If you’re just setting up sar according to this description, give the command some time to collect data.

    Commandsar -u provides information about all processors in the system, starting at midnight:

    As with top, here you need to directly check %user, %system, % iowait and hence %idle. This information may indicate how long ago the machine had problems.

    How do I troubleshoot a slow web server?

    Clean up your website code. Remove unnecessary elements such as spaces, comments, and line breaks.Check your current PHP version.MySQL Server: Look for slow queries.Analyze videos from slow sites.Speed ​​up your site.Check if you are satisfied.

    In general, some sar commands can provide a lot of information. Since this article is obviously giving a quick overview of what’s happening on the server, make sure you play man sar for more details in this article.

    To test memory performance, I use sar -r which gives the person memory usage data for that day:

    The focus of RAM input is %memused and %commit. A few words about the %commit field: this field can show more than 100% because the Linux kernel regularly overwrites RAM. If %commit consistently exceeds 100%, this may indicate that the system needs more RAM.

    How do I fix a slow running Linux server problem?

    Step 1: Check for I/O slowdown and CPU idle time.Step 2: I/O latency is low and idle hours are low: check the value CPU user time.Step 3: I/O latency is cheaper and idle time is longer.Step 4: I/O wait is high: Check swap usage.Stage 5: The use of change is great.Step 6: Adjust low usage.

    For disk I/O performance, I use sar -d, which prints your computer’s I/O output with just the name of the guitar. To get device names use sar -dP:

    linux server slow troubleshooting

    For information about this type of output, see

    LÖST: Förslag För Felsökning Av En Långsam Linux-server.
    OPGELOST: Suggesties Voor Het Oplossen Van Problemen Met Een Trage Linux-server.
    РЕШЕНО: предложения по устранению неполадок с медленным сервером Linux.
    ROZWIĄZANE: Sugestie Dotyczące Rozwiązywania Problemów Z Powolnym Serwerem Linux.
    RÉSOLU : Suggestions Pour Dépanner Un Serveur Linux Lent.
    해결: 느린 Linux 서버 문제 해결을 위한 제안.
    BEHOBEN: Vorschläge Zur Fehlerbehebung Bei Einem Langsamen Linux-Server.
    RESOLVIDO: Sugestões Para Solucionar Problemas De Um Servidor Linux Lento.
    SOLUCIONADO: Sugerencias Para Solucionar Problemas De Un Servidor Linux Lento.
    RISOLTO: Suggerimenti Per La Risoluzione Dei Problemi Di Un Server Linux Lento.