for what My mysql server get mr than 2 gig RAM on my vps?Less RAM than Index_length MyISAMMySQL replication...

What are some ways of extending a description of a scenery?

How to politely refuse in-office gym instructor for steroids and protein

Is Screenshot Time-tracking Common?

What is a good reason for every spaceship to carry gun on board?

Is it possible to rotate the Isolines on a Surface Using `MeshFunction`?

Was there a pre-determined arrangement for the division of Germany in case it surrendered before any Soviet forces entered its territory?

Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?

What can I do to encourage my players to use their consumables?

Single-row INSERT...SELECT much slower than separate SELECT

Sharepoint metadata URL

Other than edits for international editions, did Harry Potter and the Philosopher's Stone receive errata?

How to completely remove a package in Ubuntu (like it never existed)

Why did Luke use his left hand to shoot?

How can I prevent an oracle who can see into the past from knowing everything that has happened?

Why do neural networks need so many examples to perform?

How is this property called for mod?

How can I handle players killing my NPC outside of combat?

Need help with a circuit diagram where the motor does not seem to have any connection to ground. Error with diagram? Or am i missing something?

Is it possible to detect 100% of SQLi with a simple regex?

Why does 0.-5 evaluate to -5?

How do you get out of your own psychology to write characters?

Are all power cords made equal?

What species should be used for storage of human minds?

Minimum Viable Product for RTS game?



for what My mysql server get mr than 2 gig RAM on my vps?


Less RAM than Index_length MyISAMMySQL replication between VPS and shared hostMySQL Config for server with 8gb RAM and 4 cpusOptimise MySQL on VPS (2 CPUs & 3 GB RAM) with WP MUMySql crashes in VPSSOLUTION - OOM Killer was killing mariadb every hour or soRAM for dedicated MySQL serverOptimize InnoDB settings for current VPS setupMysql service stop suddenly in VPSMySQL consuming too much memory













1















imnot know english very well so sory for my bad dictation



on my vps that has 4 gigabyte RAM and 4 core CPU and 220 gig HDD .
i haved installed centos basic server 6.5 x64 and virtualmin last version upto today .
but after installing and setup a BIND Server and a simple virtual host over Nginx web server



i saw that have 12 proccess that allocated 840 MB of my RAM
thats proccess named in htop : mysqld



for what ?



and how to solve this problem ?



screen shot of htopscreen shot of virtualmin panel



thanks for all










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    1















    imnot know english very well so sory for my bad dictation



    on my vps that has 4 gigabyte RAM and 4 core CPU and 220 gig HDD .
    i haved installed centos basic server 6.5 x64 and virtualmin last version upto today .
    but after installing and setup a BIND Server and a simple virtual host over Nginx web server



    i saw that have 12 proccess that allocated 840 MB of my RAM
    thats proccess named in htop : mysqld



    for what ?



    and how to solve this problem ?



    screen shot of htopscreen shot of virtualmin panel



    thanks for all










    share|improve this question














    bumped to the homepage by Community 5 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      1












      1








      1








      imnot know english very well so sory for my bad dictation



      on my vps that has 4 gigabyte RAM and 4 core CPU and 220 gig HDD .
      i haved installed centos basic server 6.5 x64 and virtualmin last version upto today .
      but after installing and setup a BIND Server and a simple virtual host over Nginx web server



      i saw that have 12 proccess that allocated 840 MB of my RAM
      thats proccess named in htop : mysqld



      for what ?



      and how to solve this problem ?



      screen shot of htopscreen shot of virtualmin panel



      thanks for all










      share|improve this question














      imnot know english very well so sory for my bad dictation



      on my vps that has 4 gigabyte RAM and 4 core CPU and 220 gig HDD .
      i haved installed centos basic server 6.5 x64 and virtualmin last version upto today .
      but after installing and setup a BIND Server and a simple virtual host over Nginx web server



      i saw that have 12 proccess that allocated 840 MB of my RAM
      thats proccess named in htop : mysqld



      for what ?



      and how to solve this problem ?



      screen shot of htopscreen shot of virtualmin panel



      thanks for all







      mysql centos






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 16 '14 at 22:05









      A SED KHOSROA SED KHOSRO

      61




      61





      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          What you are seeing on htop are not processes, but "light processes" or more commonly named "threads". MySQL will only use one process for its server (plus one for its wrapper/watchdog mysqld_safe. You can check that by executing pstree, which will show clearly differentiated the child threads with curly braces, for example:



          init─┬─agetty
          ├─atd
          ├─auditd───{auditd}
          ├─crond
          ├─dbus-daemon
          ├─dhclient
          ├─httpd───8*[httpd]
          ├─6*[mingetty]
          ├─mysqld_safe───mysqld───33*[{mysqld}]
          ├─nagios───{nagios}
          ├─ntpd
          ├─rsyslogd───3*[{rsyslogd}]
          ├─2*[sendmail]
          ├─sshd───sshd───sshd───bash───pstree
          └─udevd───udevd


          MySQL is a "single process" executable, but it is multithreaded, which means that it will use a separate thread for each SQL connection, plus some additional ones for so called "background processes". This is a good thing because if the server is idle, it will not take extra memory (memory is shared with all the other threads), but if the server is busy, it can parallelize tasks like IO writes, read-aheads, unnecessary-data purges and secondary index changes (for example, for InnoDB). Again, that is a good thing and not a problem. All the threads together are using 840MB, not each of them. That is something that htop may not be very clear about.



          If you didn't installed manually MySQL, you should investigate which of your services installed requires it and what it is being used for.



          If 840MB is too much for mysqld on your 2GB ram server, as it may not be a dedicated server, I can tell you ways to minimize memory usage my changing its configuration:




          • Disable the performance-schema metrics

          • Disable your query cache

          • Reduce your buffer pool size (defaults to 128 MB)

          • Reduce per-connection usage by setting per-conection buffers lower (sort-buffer-size, join-buffer-size, etc.) and reducing the number of concurrent connections (max-connections)


          Obviously, some of these will reduce your performance and/or drop functionality. Some of them require a server restart.



          Please also note that memory usage being maximised is usually a good thing, as memory not used directly by applications tends to be used for filesystem cache, making disk access faster. Unless you do not have swapping activity (or predict to have it), memory usage is a good thing.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            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',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f74174%2ffor-what-my-mysql-server-get-mr-than-2-gig-ram-on-my-vps%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            What you are seeing on htop are not processes, but "light processes" or more commonly named "threads". MySQL will only use one process for its server (plus one for its wrapper/watchdog mysqld_safe. You can check that by executing pstree, which will show clearly differentiated the child threads with curly braces, for example:



            init─┬─agetty
            ├─atd
            ├─auditd───{auditd}
            ├─crond
            ├─dbus-daemon
            ├─dhclient
            ├─httpd───8*[httpd]
            ├─6*[mingetty]
            ├─mysqld_safe───mysqld───33*[{mysqld}]
            ├─nagios───{nagios}
            ├─ntpd
            ├─rsyslogd───3*[{rsyslogd}]
            ├─2*[sendmail]
            ├─sshd───sshd───sshd───bash───pstree
            └─udevd───udevd


            MySQL is a "single process" executable, but it is multithreaded, which means that it will use a separate thread for each SQL connection, plus some additional ones for so called "background processes". This is a good thing because if the server is idle, it will not take extra memory (memory is shared with all the other threads), but if the server is busy, it can parallelize tasks like IO writes, read-aheads, unnecessary-data purges and secondary index changes (for example, for InnoDB). Again, that is a good thing and not a problem. All the threads together are using 840MB, not each of them. That is something that htop may not be very clear about.



            If you didn't installed manually MySQL, you should investigate which of your services installed requires it and what it is being used for.



            If 840MB is too much for mysqld on your 2GB ram server, as it may not be a dedicated server, I can tell you ways to minimize memory usage my changing its configuration:




            • Disable the performance-schema metrics

            • Disable your query cache

            • Reduce your buffer pool size (defaults to 128 MB)

            • Reduce per-connection usage by setting per-conection buffers lower (sort-buffer-size, join-buffer-size, etc.) and reducing the number of concurrent connections (max-connections)


            Obviously, some of these will reduce your performance and/or drop functionality. Some of them require a server restart.



            Please also note that memory usage being maximised is usually a good thing, as memory not used directly by applications tends to be used for filesystem cache, making disk access faster. Unless you do not have swapping activity (or predict to have it), memory usage is a good thing.






            share|improve this answer






























              0














              What you are seeing on htop are not processes, but "light processes" or more commonly named "threads". MySQL will only use one process for its server (plus one for its wrapper/watchdog mysqld_safe. You can check that by executing pstree, which will show clearly differentiated the child threads with curly braces, for example:



              init─┬─agetty
              ├─atd
              ├─auditd───{auditd}
              ├─crond
              ├─dbus-daemon
              ├─dhclient
              ├─httpd───8*[httpd]
              ├─6*[mingetty]
              ├─mysqld_safe───mysqld───33*[{mysqld}]
              ├─nagios───{nagios}
              ├─ntpd
              ├─rsyslogd───3*[{rsyslogd}]
              ├─2*[sendmail]
              ├─sshd───sshd───sshd───bash───pstree
              └─udevd───udevd


              MySQL is a "single process" executable, but it is multithreaded, which means that it will use a separate thread for each SQL connection, plus some additional ones for so called "background processes". This is a good thing because if the server is idle, it will not take extra memory (memory is shared with all the other threads), but if the server is busy, it can parallelize tasks like IO writes, read-aheads, unnecessary-data purges and secondary index changes (for example, for InnoDB). Again, that is a good thing and not a problem. All the threads together are using 840MB, not each of them. That is something that htop may not be very clear about.



              If you didn't installed manually MySQL, you should investigate which of your services installed requires it and what it is being used for.



              If 840MB is too much for mysqld on your 2GB ram server, as it may not be a dedicated server, I can tell you ways to minimize memory usage my changing its configuration:




              • Disable the performance-schema metrics

              • Disable your query cache

              • Reduce your buffer pool size (defaults to 128 MB)

              • Reduce per-connection usage by setting per-conection buffers lower (sort-buffer-size, join-buffer-size, etc.) and reducing the number of concurrent connections (max-connections)


              Obviously, some of these will reduce your performance and/or drop functionality. Some of them require a server restart.



              Please also note that memory usage being maximised is usually a good thing, as memory not used directly by applications tends to be used for filesystem cache, making disk access faster. Unless you do not have swapping activity (or predict to have it), memory usage is a good thing.






              share|improve this answer




























                0












                0








                0







                What you are seeing on htop are not processes, but "light processes" or more commonly named "threads". MySQL will only use one process for its server (plus one for its wrapper/watchdog mysqld_safe. You can check that by executing pstree, which will show clearly differentiated the child threads with curly braces, for example:



                init─┬─agetty
                ├─atd
                ├─auditd───{auditd}
                ├─crond
                ├─dbus-daemon
                ├─dhclient
                ├─httpd───8*[httpd]
                ├─6*[mingetty]
                ├─mysqld_safe───mysqld───33*[{mysqld}]
                ├─nagios───{nagios}
                ├─ntpd
                ├─rsyslogd───3*[{rsyslogd}]
                ├─2*[sendmail]
                ├─sshd───sshd───sshd───bash───pstree
                └─udevd───udevd


                MySQL is a "single process" executable, but it is multithreaded, which means that it will use a separate thread for each SQL connection, plus some additional ones for so called "background processes". This is a good thing because if the server is idle, it will not take extra memory (memory is shared with all the other threads), but if the server is busy, it can parallelize tasks like IO writes, read-aheads, unnecessary-data purges and secondary index changes (for example, for InnoDB). Again, that is a good thing and not a problem. All the threads together are using 840MB, not each of them. That is something that htop may not be very clear about.



                If you didn't installed manually MySQL, you should investigate which of your services installed requires it and what it is being used for.



                If 840MB is too much for mysqld on your 2GB ram server, as it may not be a dedicated server, I can tell you ways to minimize memory usage my changing its configuration:




                • Disable the performance-schema metrics

                • Disable your query cache

                • Reduce your buffer pool size (defaults to 128 MB)

                • Reduce per-connection usage by setting per-conection buffers lower (sort-buffer-size, join-buffer-size, etc.) and reducing the number of concurrent connections (max-connections)


                Obviously, some of these will reduce your performance and/or drop functionality. Some of them require a server restart.



                Please also note that memory usage being maximised is usually a good thing, as memory not used directly by applications tends to be used for filesystem cache, making disk access faster. Unless you do not have swapping activity (or predict to have it), memory usage is a good thing.






                share|improve this answer















                What you are seeing on htop are not processes, but "light processes" or more commonly named "threads". MySQL will only use one process for its server (plus one for its wrapper/watchdog mysqld_safe. You can check that by executing pstree, which will show clearly differentiated the child threads with curly braces, for example:



                init─┬─agetty
                ├─atd
                ├─auditd───{auditd}
                ├─crond
                ├─dbus-daemon
                ├─dhclient
                ├─httpd───8*[httpd]
                ├─6*[mingetty]
                ├─mysqld_safe───mysqld───33*[{mysqld}]
                ├─nagios───{nagios}
                ├─ntpd
                ├─rsyslogd───3*[{rsyslogd}]
                ├─2*[sendmail]
                ├─sshd───sshd───sshd───bash───pstree
                └─udevd───udevd


                MySQL is a "single process" executable, but it is multithreaded, which means that it will use a separate thread for each SQL connection, plus some additional ones for so called "background processes". This is a good thing because if the server is idle, it will not take extra memory (memory is shared with all the other threads), but if the server is busy, it can parallelize tasks like IO writes, read-aheads, unnecessary-data purges and secondary index changes (for example, for InnoDB). Again, that is a good thing and not a problem. All the threads together are using 840MB, not each of them. That is something that htop may not be very clear about.



                If you didn't installed manually MySQL, you should investigate which of your services installed requires it and what it is being used for.



                If 840MB is too much for mysqld on your 2GB ram server, as it may not be a dedicated server, I can tell you ways to minimize memory usage my changing its configuration:




                • Disable the performance-schema metrics

                • Disable your query cache

                • Reduce your buffer pool size (defaults to 128 MB)

                • Reduce per-connection usage by setting per-conection buffers lower (sort-buffer-size, join-buffer-size, etc.) and reducing the number of concurrent connections (max-connections)


                Obviously, some of these will reduce your performance and/or drop functionality. Some of them require a server restart.



                Please also note that memory usage being maximised is usually a good thing, as memory not used directly by applications tends to be used for filesystem cache, making disk access faster. Unless you do not have swapping activity (or predict to have it), memory usage is a good thing.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Aug 18 '14 at 14:41

























                answered Aug 17 '14 at 10:15









                jynusjynus

                11.1k11832




                11.1k11832






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f74174%2ffor-what-my-mysql-server-get-mr-than-2-gig-ram-on-my-vps%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Szabolcs (Ungheria) Altri progetti | Menu di navigazione48°10′14.56″N 21°29′33.14″E /...

                    Discografia di Klaus Schulze Indice Album in studio | Album dal vivo | Singoli | Antologie | Colonne...

                    How to make inet_server_addr() return localhost in spite of ::1/128RETURN NEXT in Postgres FunctionConnect to...