Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
09-21-2004, 08:07 AM
|
#1
|
|
LQ Newbie
Registered: Aug 2003
Posts: 19
Rep:
|
Growing MySQL footprint
Hi,
According to 'top', the memory usage for each of my 'mysqld' processes appears to be increasing as the database grows.
Is this normal?
Thanks,
Rob
|
|
|
|
09-22-2004, 07:29 AM
|
#2
|
|
Member
Registered: Jul 2001
Location: india
Distribution: RedHat 7.1,7.2,7.3, 8.0,9.0,Fedora,EL2.1,EL3.0
Posts: 103
Rep:
|
Hi,
I am not very sure, but that is exactly what I also have seen. But this does not depend on the database size. It depends more on that time that this database is running. All you need to do is restart the mysqld process when you think that the footprint has increased to a high value.
Regards
Subhasis Ray
|
|
|
|
09-22-2004, 08:28 AM
|
#3
|
|
Senior Member
Registered: Dec 2002
Location: England
Distribution: Used to use Mandrake/Mandriva
Posts: 2,794
Rep: 
|
subhasis_ray, that sounds wrong and possibly like a memory leak. Check any updates for your DBMS version.
robbiemorgan, yes as the data which a process handles grows so must the memory allocated to the process to hold and manipulate that data. 
|
|
|
|
09-22-2004, 08:37 AM
|
#4
|
|
LQ Newbie
Registered: Aug 2003
Posts: 19
Original Poster
Rep:
|
Hi Proud,
Ok, but 99% of the queries I'm running on the larger tables are INSERTs, the tables on which I'm doing SELECTs only have a handful of rows a piece.
Is there a way to optimize this? Otherwise the DB will eventually grow so big it saps all my memory.
I guess the other option is to periodically dump the data into a separate offline DB - keep the live DB lean...
Thanks,
Rob
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 12:27 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|