View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us
Community ▶ Questions ▶ MySQL memory footprint
Log in to Ask a Question

MySQL memory footprint

development

Running MySQL on my Linode 720 to support Gallery2. After a week or two uptime, memory for MySQL climbs to 340M.

I initially tuned MySQL based on recommendations from http://www.day32.com/MySQL/ and http://wiki.mysqltuner.com/MySQLTuner

I'll be the 1st to admit I don't know much about administering MySQL.

Anyway, I'd like to reduce memory to <= 300M. Any recommendation on where to start? Here's my config: http://donsbox.com/~dfelicia/my.cnf

2 Replies

Do you actually need the features that InnoDB tables provide? It looks like about half of the memory usage you're seeing might be attributable to that. I have InnoDB turned off and–though my DBs are very small--MySQL never goes about 20MB total usage.

A long time ago, when Linode's small plan was 64MB of memory, caker put together this my.cnf to help us all get MySQL to fit. I've been using the same my.cnf (with minor modifications) since then. http://www.linode.com/~caker/uml/my.cnf

-James

> Do you actually need the features that InnoDB tables provide? It looks like about half of the memory usage you're seeing might be attributable to that.
Yep. Gallery uses innodb.

Can I do the opposite? Can I turn off MyISAM, or lower keybuffersize without adversely affecting things? I'm not using MySQL for anything other than gallery.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Log in to Reply
Community Code of Conduct