One of the first steps when addressing a MySQL performance tuning problem is to perform a system audit of the physical hardware resources, then identify any obvious bottlenecks in these resources.

When dealing with CPU, a quick audit should include identifying the number of CPU cores your server has, and the types of these cores. The key file on Linux systems is /proc/cpuinfo.

Number of cores can be found via the command cat /proc/cpuinfo | grep “^processor” | wc -l

You need to look more closely at the file to determine the type of CPU (e.g. below the model name shows Intel(R) Xeon(R) CPU X3220 @ 2.40GHz. The combination of knowing the number of processors (cores) listed and physical id and siblings helps identify how many CPUs and how many cores per CPU exist.

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model …

The annual MySQL Conference & Expo will be held in this year on April 20-23 in Santa Clara, California with a double twist.

Not one, but *two* FREE additional MySQL Conferences are running at the same time, in the same hotel. If you on the west coast you can effectively get a free conference with many MySQL experts speaking at them. I am speaking at all three on three different topics.

The first announcement was the 2009 MySQL Camp organized by Sheeri K. Cabral - The She-BA in line with the O’Reilly approach of having a smaller un-conference within a conference such as with Web 2.0 NY last year.

However the big news was the …

Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

Here are some quotes from a recent article talking about Oracle's maintenance and support fees:

Before Oracle acquired BEA earlier this year, the company charged 18% to 20% for support and maintenance. Oracle increased those fees to meet its own structure and also raised list prices on most BEA products.

That didn't sit well.

and


One Java-centric VAR, who spoke on the condition of anonymity, said some of his BEA WebLogic customers are moving to alternative application servers just to get away from Oracle.

and

"What company comes in this climate and not only jacks up prices but support prices as …

While working with Monty Widenius on a bug I reported in MariaDB I was surprised to not get an IRC response for a few minutes. When committed Monty can identify, create a workaround, and patch a problem in code before you have time to read all the responses he also types. See my Monty’s Monument “Passion is a timeless wisdom” comment. One thing I forgot to say in that entry was, while 9pm in New york, it was at last 3am-5am Monty time.

We all love memorable quotes, so here is one.

“sorry, machine died; First time in years”

[9:40pm] montywi: then just try compiling mysqld.o, no need to wait for everything else...
....
[9:58pm] rbradfor: make is clean.
[9:59pm] montywi: sorry, machine died;  First time in years
[10:00pm] rbradfor: laughs …

In the last three updates to this blog, I've tried to set out a clear direction of where Sun's headed. I've talked about our three basic priorities:

1. Technology Adoption
2. Commercial Innovation
3. Efficiently Connecting Adoption and Commercial Opportunity.

I'm hoping you've got a clear picture surrounding the first of these two priorities - how and where we drive software adoption, and focus our commercial efforts.

So now I'd like to talk about the linkages - while also addressing one of our biggest strategic challenges, our scale.

Selling Scale

First, why is scale a challenge for Sun? To be clear, I'm not talking about purchasing scale. As I've said before, we use innovation to drive product profitability, not simply bulk purchasing leverage. The scale to which I'm referring is selling and marketing scale. With Sun's current products, we could be selling to twice …

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....

My previous blog entry on MySQL scalability on the T5440 is now completed by a Sun BluePrint that you can find here.

See you next time in the wonderful world of benchmarking....