Ubuntu 18.04 too slow

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite












I migrated to Ubuntu 18.04 a week ago due my VPN needs, and it works perfectly except that the OS is too slow and I sometimes can't open any applications until I reboot.



My laptop has good hardware (a seventh-generation Intel Core i7 and 8 GB of RAM), but my memory utilization is 6 GB or more when I run Skype, Slack, and Firefox together.



Is this normal?




vmstat 10 4 output:



procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
7 0 0 898448 56344 3007108 0 0 148 215 420 1246 12 4 78 7 0
7 0 0 887908 56376 3059492 0 0 1 68 4231 13951 33 10 56 0 0
7 0 0 943000 56416 2996092 0 0 0 102 4199 14527 32 10 58 0 0
3 0 0 934796 56448 3003276 0 0 23 103 4397 14711 34 10 55 1 0






share|improve this question






















  • I read about the leak memory, but my gnome version is already the correct one
    – Helder Júnior
    May 18 at 7:28










  • Would you please post details about vmstat 10 4 please? Have you checked the process list?
    – Uqbar
    May 18 at 8:24










  • how you can the see in this image ibb.co/eRMSLd
    – Helder Júnior
    May 18 at 9:02










  • Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
    – Chai T. Rex
    May 19 at 21:59







  • 2




    Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
    – Chai T. Rex
    May 19 at 22:00















up vote
3
down vote

favorite












I migrated to Ubuntu 18.04 a week ago due my VPN needs, and it works perfectly except that the OS is too slow and I sometimes can't open any applications until I reboot.



My laptop has good hardware (a seventh-generation Intel Core i7 and 8 GB of RAM), but my memory utilization is 6 GB or more when I run Skype, Slack, and Firefox together.



Is this normal?




vmstat 10 4 output:



procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
7 0 0 898448 56344 3007108 0 0 148 215 420 1246 12 4 78 7 0
7 0 0 887908 56376 3059492 0 0 1 68 4231 13951 33 10 56 0 0
7 0 0 943000 56416 2996092 0 0 0 102 4199 14527 32 10 58 0 0
3 0 0 934796 56448 3003276 0 0 23 103 4397 14711 34 10 55 1 0






share|improve this question






















  • I read about the leak memory, but my gnome version is already the correct one
    – Helder Júnior
    May 18 at 7:28










  • Would you please post details about vmstat 10 4 please? Have you checked the process list?
    – Uqbar
    May 18 at 8:24










  • how you can the see in this image ibb.co/eRMSLd
    – Helder Júnior
    May 18 at 9:02










  • Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
    – Chai T. Rex
    May 19 at 21:59







  • 2




    Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
    – Chai T. Rex
    May 19 at 22:00













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I migrated to Ubuntu 18.04 a week ago due my VPN needs, and it works perfectly except that the OS is too slow and I sometimes can't open any applications until I reboot.



My laptop has good hardware (a seventh-generation Intel Core i7 and 8 GB of RAM), but my memory utilization is 6 GB or more when I run Skype, Slack, and Firefox together.



Is this normal?




vmstat 10 4 output:



procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
7 0 0 898448 56344 3007108 0 0 148 215 420 1246 12 4 78 7 0
7 0 0 887908 56376 3059492 0 0 1 68 4231 13951 33 10 56 0 0
7 0 0 943000 56416 2996092 0 0 0 102 4199 14527 32 10 58 0 0
3 0 0 934796 56448 3003276 0 0 23 103 4397 14711 34 10 55 1 0






share|improve this question














I migrated to Ubuntu 18.04 a week ago due my VPN needs, and it works perfectly except that the OS is too slow and I sometimes can't open any applications until I reboot.



My laptop has good hardware (a seventh-generation Intel Core i7 and 8 GB of RAM), but my memory utilization is 6 GB or more when I run Skype, Slack, and Firefox together.



Is this normal?




vmstat 10 4 output:



procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
7 0 0 898448 56344 3007108 0 0 148 215 420 1246 12 4 78 7 0
7 0 0 887908 56376 3059492 0 0 1 68 4231 13951 33 10 56 0 0
7 0 0 943000 56416 2996092 0 0 0 102 4199 14527 32 10 58 0 0
3 0 0 934796 56448 3003276 0 0 23 103 4397 14711 34 10 55 1 0








share|improve this question













share|improve this question




share|improve this question








edited May 19 at 22:26









Chai T. Rex

3,45611132




3,45611132










asked May 18 at 7:27









Helder Júnior

3113




3113











  • I read about the leak memory, but my gnome version is already the correct one
    – Helder Júnior
    May 18 at 7:28










  • Would you please post details about vmstat 10 4 please? Have you checked the process list?
    – Uqbar
    May 18 at 8:24










  • how you can the see in this image ibb.co/eRMSLd
    – Helder Júnior
    May 18 at 9:02










  • Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
    – Chai T. Rex
    May 19 at 21:59







  • 2




    Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
    – Chai T. Rex
    May 19 at 22:00

















  • I read about the leak memory, but my gnome version is already the correct one
    – Helder Júnior
    May 18 at 7:28










  • Would you please post details about vmstat 10 4 please? Have you checked the process list?
    – Uqbar
    May 18 at 8:24










  • how you can the see in this image ibb.co/eRMSLd
    – Helder Júnior
    May 18 at 9:02










  • Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
    – Chai T. Rex
    May 19 at 21:59







  • 2




    Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
    – Chai T. Rex
    May 19 at 22:00
















I read about the leak memory, but my gnome version is already the correct one
– Helder Júnior
May 18 at 7:28




I read about the leak memory, but my gnome version is already the correct one
– Helder Júnior
May 18 at 7:28












Would you please post details about vmstat 10 4 please? Have you checked the process list?
– Uqbar
May 18 at 8:24




Would you please post details about vmstat 10 4 please? Have you checked the process list?
– Uqbar
May 18 at 8:24












how you can the see in this image ibb.co/eRMSLd
– Helder Júnior
May 18 at 9:02




how you can the see in this image ibb.co/eRMSLd
– Helder Júnior
May 18 at 9:02












Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
– Chai T. Rex
May 19 at 21:59





Ubuntu hasn't yet published a fix to that GNOME memory leak (status is still In Progress). GNOME people are still working on it.
– Chai T. Rex
May 19 at 21:59





2




2




Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
– Chai T. Rex
May 19 at 22:00





Please don't use screenshots for terminal output. Instead, edit your question, paste in the terminal output, select the terminal output in the question editor, press the button in the editor, and save the edits.
– Chai T. Rex
May 19 at 22:00











2 Answers
2






active

oldest

votes

















up vote
2
down vote













High memory utilization is quite normal on a Linux system. Ubuntu is no exception. It uses unused memory for disk caching to increase system performance. You can find a good explanation with some further detail here.



Slow speed is often more a function of DE weight (gnome is heavy) than distribution version. LXDE and XFCE are very light and can make even low quality or somewhat obsolete hardware deliver acceptable performance.



Other things that can drastically reduce system speed are failing or poorly performing storage devices, dusty or otherwise compromised cooling systems can lead to overheat conditions that will cause modern processors to reduce speed in an attempt at self preservation.



The output of commands like dmesg and grep "error" /var/log/syslog can also provide clues as to what's going wrong in a system that doesn't perform as expected.



This is by no means a complete list, but it should give you some clues, and may very well lead you to new and more focused questions.



The memory leak bug you mention doesn't appear to have been squashed yet, although it has been assigned. However your vmstat output doesn't appear to indicate that you are effected by that bug.



According to your vmstat output your CPU is spending the majority of it's time idle, so the bottleneck isn't there. My best guess given the information available is either storage device or cooling system problems.






share|improve this answer






















  • @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
    – Elder Geek
    Jun 14 at 13:17

















up vote
1
down vote













Some common reasons you can't open any applications are:



  1. The system didn't notice you tried to open the application. Try to open the application once more (don't do this repeatedly or you might suddenly have the application open 25 times or something).

  2. The system might be really, really busy. Leave the computer alone for literally five minutes right after you try to open the application and see if the application opens.

  3. Virtual memory might be almost completely full. Check whether RAM and swap space are completely filled by running free -m or top in a terminal.

  4. Your disk might be failing. Run an Extended SMART test in the Disks application. It'll take several hours to complete the test, but you can use your computer while that's going on. If you need to reboot while the test is running, go ahead: the test will pick up right where it left off when your computer comes back up.

  5. Your RAM might be bad. Reboot and hold down Left Shift or Esc while it's booting to bring up the GRUB menu. Select Memory test (memtest86+). Make sure your computer is plugged in and its air vents aren't blocked, because this test can use a lot of energy and heat the computer up quite a bit. Let it run overnight while you sleep. See if the error count is over zero when you wake up.





share|improve this answer






















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037668%2fubuntu-18-04-too-slow%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    High memory utilization is quite normal on a Linux system. Ubuntu is no exception. It uses unused memory for disk caching to increase system performance. You can find a good explanation with some further detail here.



    Slow speed is often more a function of DE weight (gnome is heavy) than distribution version. LXDE and XFCE are very light and can make even low quality or somewhat obsolete hardware deliver acceptable performance.



    Other things that can drastically reduce system speed are failing or poorly performing storage devices, dusty or otherwise compromised cooling systems can lead to overheat conditions that will cause modern processors to reduce speed in an attempt at self preservation.



    The output of commands like dmesg and grep "error" /var/log/syslog can also provide clues as to what's going wrong in a system that doesn't perform as expected.



    This is by no means a complete list, but it should give you some clues, and may very well lead you to new and more focused questions.



    The memory leak bug you mention doesn't appear to have been squashed yet, although it has been assigned. However your vmstat output doesn't appear to indicate that you are effected by that bug.



    According to your vmstat output your CPU is spending the majority of it's time idle, so the bottleneck isn't there. My best guess given the information available is either storage device or cooling system problems.






    share|improve this answer






















    • @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
      – Elder Geek
      Jun 14 at 13:17














    up vote
    2
    down vote













    High memory utilization is quite normal on a Linux system. Ubuntu is no exception. It uses unused memory for disk caching to increase system performance. You can find a good explanation with some further detail here.



    Slow speed is often more a function of DE weight (gnome is heavy) than distribution version. LXDE and XFCE are very light and can make even low quality or somewhat obsolete hardware deliver acceptable performance.



    Other things that can drastically reduce system speed are failing or poorly performing storage devices, dusty or otherwise compromised cooling systems can lead to overheat conditions that will cause modern processors to reduce speed in an attempt at self preservation.



    The output of commands like dmesg and grep "error" /var/log/syslog can also provide clues as to what's going wrong in a system that doesn't perform as expected.



    This is by no means a complete list, but it should give you some clues, and may very well lead you to new and more focused questions.



    The memory leak bug you mention doesn't appear to have been squashed yet, although it has been assigned. However your vmstat output doesn't appear to indicate that you are effected by that bug.



    According to your vmstat output your CPU is spending the majority of it's time idle, so the bottleneck isn't there. My best guess given the information available is either storage device or cooling system problems.






    share|improve this answer






















    • @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
      – Elder Geek
      Jun 14 at 13:17












    up vote
    2
    down vote










    up vote
    2
    down vote









    High memory utilization is quite normal on a Linux system. Ubuntu is no exception. It uses unused memory for disk caching to increase system performance. You can find a good explanation with some further detail here.



    Slow speed is often more a function of DE weight (gnome is heavy) than distribution version. LXDE and XFCE are very light and can make even low quality or somewhat obsolete hardware deliver acceptable performance.



    Other things that can drastically reduce system speed are failing or poorly performing storage devices, dusty or otherwise compromised cooling systems can lead to overheat conditions that will cause modern processors to reduce speed in an attempt at self preservation.



    The output of commands like dmesg and grep "error" /var/log/syslog can also provide clues as to what's going wrong in a system that doesn't perform as expected.



    This is by no means a complete list, but it should give you some clues, and may very well lead you to new and more focused questions.



    The memory leak bug you mention doesn't appear to have been squashed yet, although it has been assigned. However your vmstat output doesn't appear to indicate that you are effected by that bug.



    According to your vmstat output your CPU is spending the majority of it's time idle, so the bottleneck isn't there. My best guess given the information available is either storage device or cooling system problems.






    share|improve this answer














    High memory utilization is quite normal on a Linux system. Ubuntu is no exception. It uses unused memory for disk caching to increase system performance. You can find a good explanation with some further detail here.



    Slow speed is often more a function of DE weight (gnome is heavy) than distribution version. LXDE and XFCE are very light and can make even low quality or somewhat obsolete hardware deliver acceptable performance.



    Other things that can drastically reduce system speed are failing or poorly performing storage devices, dusty or otherwise compromised cooling systems can lead to overheat conditions that will cause modern processors to reduce speed in an attempt at self preservation.



    The output of commands like dmesg and grep "error" /var/log/syslog can also provide clues as to what's going wrong in a system that doesn't perform as expected.



    This is by no means a complete list, but it should give you some clues, and may very well lead you to new and more focused questions.



    The memory leak bug you mention doesn't appear to have been squashed yet, although it has been assigned. However your vmstat output doesn't appear to indicate that you are effected by that bug.



    According to your vmstat output your CPU is spending the majority of it's time idle, so the bottleneck isn't there. My best guess given the information available is either storage device or cooling system problems.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jun 14 at 13:19

























    answered May 19 at 21:52









    Elder Geek

    25.2k948119




    25.2k948119











    • @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
      – Elder Geek
      Jun 14 at 13:17
















    • @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
      – Elder Geek
      Jun 14 at 13:17















    @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
    – Elder Geek
    Jun 14 at 13:17




    @HelderJúnior Always happy to help. Since your a new member here, I should let you know that the way we say thanks here is by accepting(clicking the check mark) next to the answer that helped us the most and or upvoting. upvoting will be the next privilege that you receive as your reputation increases here.
    – Elder Geek
    Jun 14 at 13:17












    up vote
    1
    down vote













    Some common reasons you can't open any applications are:



    1. The system didn't notice you tried to open the application. Try to open the application once more (don't do this repeatedly or you might suddenly have the application open 25 times or something).

    2. The system might be really, really busy. Leave the computer alone for literally five minutes right after you try to open the application and see if the application opens.

    3. Virtual memory might be almost completely full. Check whether RAM and swap space are completely filled by running free -m or top in a terminal.

    4. Your disk might be failing. Run an Extended SMART test in the Disks application. It'll take several hours to complete the test, but you can use your computer while that's going on. If you need to reboot while the test is running, go ahead: the test will pick up right where it left off when your computer comes back up.

    5. Your RAM might be bad. Reboot and hold down Left Shift or Esc while it's booting to bring up the GRUB menu. Select Memory test (memtest86+). Make sure your computer is plugged in and its air vents aren't blocked, because this test can use a lot of energy and heat the computer up quite a bit. Let it run overnight while you sleep. See if the error count is over zero when you wake up.





    share|improve this answer


























      up vote
      1
      down vote













      Some common reasons you can't open any applications are:



      1. The system didn't notice you tried to open the application. Try to open the application once more (don't do this repeatedly or you might suddenly have the application open 25 times or something).

      2. The system might be really, really busy. Leave the computer alone for literally five minutes right after you try to open the application and see if the application opens.

      3. Virtual memory might be almost completely full. Check whether RAM and swap space are completely filled by running free -m or top in a terminal.

      4. Your disk might be failing. Run an Extended SMART test in the Disks application. It'll take several hours to complete the test, but you can use your computer while that's going on. If you need to reboot while the test is running, go ahead: the test will pick up right where it left off when your computer comes back up.

      5. Your RAM might be bad. Reboot and hold down Left Shift or Esc while it's booting to bring up the GRUB menu. Select Memory test (memtest86+). Make sure your computer is plugged in and its air vents aren't blocked, because this test can use a lot of energy and heat the computer up quite a bit. Let it run overnight while you sleep. See if the error count is over zero when you wake up.





      share|improve this answer
























        up vote
        1
        down vote










        up vote
        1
        down vote









        Some common reasons you can't open any applications are:



        1. The system didn't notice you tried to open the application. Try to open the application once more (don't do this repeatedly or you might suddenly have the application open 25 times or something).

        2. The system might be really, really busy. Leave the computer alone for literally five minutes right after you try to open the application and see if the application opens.

        3. Virtual memory might be almost completely full. Check whether RAM and swap space are completely filled by running free -m or top in a terminal.

        4. Your disk might be failing. Run an Extended SMART test in the Disks application. It'll take several hours to complete the test, but you can use your computer while that's going on. If you need to reboot while the test is running, go ahead: the test will pick up right where it left off when your computer comes back up.

        5. Your RAM might be bad. Reboot and hold down Left Shift or Esc while it's booting to bring up the GRUB menu. Select Memory test (memtest86+). Make sure your computer is plugged in and its air vents aren't blocked, because this test can use a lot of energy and heat the computer up quite a bit. Let it run overnight while you sleep. See if the error count is over zero when you wake up.





        share|improve this answer














        Some common reasons you can't open any applications are:



        1. The system didn't notice you tried to open the application. Try to open the application once more (don't do this repeatedly or you might suddenly have the application open 25 times or something).

        2. The system might be really, really busy. Leave the computer alone for literally five minutes right after you try to open the application and see if the application opens.

        3. Virtual memory might be almost completely full. Check whether RAM and swap space are completely filled by running free -m or top in a terminal.

        4. Your disk might be failing. Run an Extended SMART test in the Disks application. It'll take several hours to complete the test, but you can use your computer while that's going on. If you need to reboot while the test is running, go ahead: the test will pick up right where it left off when your computer comes back up.

        5. Your RAM might be bad. Reboot and hold down Left Shift or Esc while it's booting to bring up the GRUB menu. Select Memory test (memtest86+). Make sure your computer is plugged in and its air vents aren't blocked, because this test can use a lot of energy and heat the computer up quite a bit. Let it run overnight while you sleep. See if the error count is over zero when you wake up.






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 19 at 23:02

























        answered May 19 at 22:56









        Chai T. Rex

        3,45611132




        3,45611132






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037668%2fubuntu-18-04-too-slow%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491