Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:2

Multiple mysqld instances?

posted by Krow on 06:26 AM April 29th, 2002   Printer-friendly   Email story
How many mysqld instances shold be running at a given time on a Slash system? It seems my system, when rebooted, begins one mysqld process. But after a few days, there are upwards of 20 mysqld processes running. I believe this is why my memory gets eaten up in such a hurry...(360 MB, and after 3 days, I have 13MB free...) What starts the mysqld process in Slash? I did have a bit of trouble installing, so is it possible during the numerous installs, something kept adding an entry, and now I've got many many many mysqld's running? Is this right? Thanks for any insight...
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Slash doesn't start MySQL, your OS does. Have a read through MySQL Documentation [] for more info.

    lottadot []
  • Certainly read the quite fine MySQL documentation as previously said, but also consider that linux and many other UNIX's are designed not to leave very much free memory. All of my machines have less than 10% of their memory designated as "free" after running for a few days. Disk caching dynamically uses memory that isn't otherwise being used by the system.
  • by Anonymous Coward
    I noticed this when my system started up there was a reasonable amount of ram that was used by apache and mysql. Once requests started coming in the memory was quickly used up. To solve this I changed:
    • KeepAlive
    • KeepAliveTimeout
    • MaxClients
    • MaxKeepAliveRequests
    • MaxRequestsPerChild
    • MaxSpareServers
    • MinSpareServers
    in httpd.conf to use less processes and free up processes faster. see the apache documentation http://localhost/manual/mod/core.html for the details.
  • Do a pstree. If the processes belong to different parents, then your system if starting mysqld when it shouldn't. Otherwise, if there's only one parent, then those processes are being spawned to meet demand.