Every so often people ask me the question how should they estimate memory consumption by MySQL Server in given configuration. What is the formula they could use.

The reasons to worry about memory usage are quite understandable. If you configure MySQL Server so it uses too small amount of memory it will likey perform suboptimally. If you however configure it so it consumes too much memory it may be crashing , failing to execute queries or make operation to swap seriously slowing down. On now legacy 32bit platforms you could also run out of address space so that had to be watched as well.
Having said so, I do not think looking for the secret fomula to compute your possible memory usage is the right approach to this problem. The reasons are - this formula is very complex nowadays and what is even more important "theoretically possible" maximum it provides have nothing to do with real memory consumptions. In fact typical server with 8GB of …

There have been some really cool postings at PlanetMySQL that I have been wanting to read and blog about. However, since I have been really busy (temporarily), I haven't had the chance to do so. Following is the list of posts I really liked, or would like to read at some later point.

• Podcast at Splunk.com: Brian Aker, Dana Gardner and Michael Baum talk about troubleshooting. (Thanks Markus)
  
• Zack pointed out that Sun is planning to Open Source Java
• MySQL Statement Log Analyzer (SLA) v 1.2 is now available.
• …

At the MySQL conference Timour Katchaounov presented one of my favorite sessions. I have my notes from the session speeding up queries posted on my blog.

Recently, Timour was kind enough to email me the links to his and some other talks at Google.

Overview of MySQL Engine and New Features

Cluster Talk by Stewart:

Performance tuning (Jay):

Thanks Timour!

Frank

I have been really enjoying the "How I work" series by Dave Rosenberg as it provides very good insight into how our peers work.

Here are some of my favorites (no particular order):
Brian Aker
Sheeri Kritzer
Jason Gilmore
Mike Olson

I have been really busy working on a few projects for clients and haven't been getting any free time. Hopefully this weekend I can reply to everyone who has been kind enough to email me.

Just wanted to take a moment to congratulate Markus on joining the MySQL web development team. As he says, it must feel great to work for MySQL. Man, I should have hung out with the "right guys" at the conference too ;)

Congratulations Markus, I am sure you will help MySQL conquer more heights.

- Frank

Our employee and Mayflower Fellow Thorsten Rinne develops and maintains in his sparse free time a popular FAQ management system called phpMyFAQ. Its current release is V1.6 (see press coverage on golem.de) and phpMyFAQ is licensed under MPL. Popular users of phpMyFAQ are: Stanford University, Apple, the German telecommunication company Arcor, some big E-Commerce company, Knorr Bremse AG and others.

The CVS source tree is hosted at our dev platform thinkforge.org which I mentioned in another post.

phpMyFAQ is available in 30 languages, including Chinese, …

At this week's Java One conference, newly appointed Sun CEO Jonathan Schwartz has pledged to open source Java.  This has long been a bugaboo in the open source community and it caused many to question Sun's commitment to open source.  While there have been many reasons Sun has given in the past for not wanting or needing to open source Java, such as risks of incompatibility between forked versions, these concerns have always sounded a bit overstated.

Rich Green, who has rejoined Sun as the head of software, will take responsibility for figuring out the details of how and when Sun will make it happen.  It took Sun many years of internal battles to open source Solaris, but they did it and it's now getting broader adoption than before.  You can argue whether Sun should have done these moves earlier, but lets give them …

mysqlsla v1.2 is finally done. mysqlsla is a statement log analyzer that can read and combine MySQL general and slow logs, and "raw logs." The major update with v1.2 is that it could now replace mysqldumpslow: it does nearly everything mysqldumpslow does and a lot of things mysqldumpslow doesn't. There's even an option (--mysqldumpslow or --mds) to format the results like mysqldumpslow (for nostalgia). And not that mysqldumpslow was too difficult to figure out, but mysqlsla is at least well documented. Also new with 1.2: statement filtering, statement grepping, a --safe option, analysis hiding, and re-written log parsing functions. Please report any bugs/problems.