Introduction

The purpose of this document is to explain the power-efficeincy analysis proess, power-efficiency issues and solutions in MySQL database server as an example to help identify the right tools and procedures that support the development of energy-efficient application.

Analysis Process

The remainder of the document covers the detail information on each of the above procedures 

Test Setup And MySQL Configurations

HW Installation:

So Cuil had lots of visibility because of their "data corruption" , showing "wrong" images to people.

However it seems like they still haven't cleaned up their mess.

Somehow they manage to place Geert Vanderkelen's picture in the search results for me.
Not the other way around however.

Well.. at least it isn't what they used to show :)

So Geert , if someone ever runs up to you and says "Hi Kris" , you know where they got the picture from :)

While the debate on 'what is open source' continues, the larger question of how to grow open source vendor revenue across the software market is still largely ignored READ MORE

This is the inaugural post in the weekly series "Last Week in Drizzle" where I summarize the efforts of various folks in the Drizzle community over the past week. There is a ton of enthusiasm and excitement around what is going on in Drizzle as evidenced by an explosion in the number of people tracking the mailing list and participating in coding, refactoring, testing, documentation, and general community efforts. As of this writing, 148 people are following the mailing list; this in only the second week since Brian announced Drizzle at OSCON. Pretty awesome. What is also cool is seeing a large number of MySQL engineers, consultants, and support engineers participating in the mailing list discussions and in the refactoring work.

There are now 34 folks chatting over on the Freenode #drizzle channel, and the …

I came across this error recently when trying to modify the data type of a column.

ERROR 1025 (HY000): Error on rename of './sakila/#sql-1d91_5' to './sakila/inventory' (errno: 150)

Not the first time, and not the last time. A common problem with InnoDB tables, is the lack of information, you need to dig deeper with the following command (and appropriate security a well organized security profile will NOT have).

mysql> SHOW ENGINE INNODB STATUS;

...

------------------------
LATEST FOREIGN KEY ERROR
------------------------
080717 20:00:28 Error in foreign key constraint of table sakila/inventory:
there is no index in the table which would contain
the columns as the first columns, or the data types in the
table do not match the ones in the referenced table
or one of the ON ... SET NULL columns is declared NOT NULL. Constraint:
,
  CONSTRAINT "fk_inventory_film" FOREIGN KEY ("film_id") REFERENCES "film" ("film_id") ON UPDATE CASCADE …

We recently examined a customer’s system to try to speed up an ETL (Extraction, Transformation and Loading) process for a big data set into a sort of datamart or DW.  What we typically do is ask customers to run the process in question, and then examine what’s happening.  In this case, the (very large, powerful) database server was almost completely idle, with virtually no I/O activity or CPU usage.  So we looked at the server where the ETL process was running.  It was running at 25% CPU usage and was writing some files to disk, but not waiting on I/O.

What’s going on here?  Where’s the bottleneck?  The process is slow, and neither machine is really doing much work.  Why?

Maybe you guessed the network.  Nope, not the network either.  There was plenty of spare network capacity.

If I told you the ETL machine was using exactly 25% of its CPU capacity, would you guess that …

I am very glad to hear that Brian's vision for Drizzle seems to be quite pluggable. This hits home perfectly with my hopes .. well for Drizzle to be pluggable! While I have not had the time to install and play with Drizzle I did stumble over the list of what has been dropped from MySQL so far. I am not sure how complete this list is (for example VIEW's are not listed as having been removed, but it was said that they would be removed), but I assume that nothing on the list is on there falsely. So some brief observations:

1) No windows support, not really surprised about that one. First I assume that none of the developer are interested at this point to worry about Windows, nor do I think that there is much of a Drizzle target audience running Windows servers. That being said, plenty of developer are …

High Performance MySQL, Second Edition
Optimization, Backups, Replication, and More

By Baron Schwartz , Peter Zaitsev , Vadim Tkachenko , Jeremy Zawodny , Arjen Lentz , Derek J. Balling
Second Edition June 2008
Pages: 708
ISBN 10: 0-596-10171-6 | ISBN 13: 9780596101718

When I first read about this book, I figured many sections would be over my head. I was pleasantly surprised when I …

Recently, we added information schema support to Google’s userstats patch.

There are three information schema tables added: user_statistics, table_statistics, index_statistics.

One can now use select * from information_schema.user_statistics along with show user_statistics.

Links:
Patch for 5.0.62
Patch for 5.1.26

Entry posted by Evgeniy | 16 comments

Add to: …

The Drizzle Report is a weekly synopsis on drizzle development. This first report will contain more than just a weeks worth of development in order to catch up.

What has been removed from the initial MySQL source tree can be found at the MySQL Differences wiki page. Some of the highlights were the removal of the mysql database, TINY/MED/LONG BLOB, TINY/MED/LONG TEXT thespatial data types, and FULLTEXT indexes. Certain keywords were removed too like ENGINES, CLIENT and CONTRIBUTORS. Even drizzleadmin has been stripped down to just ping and shutdown.The long-standing MySQL ACL has been ripped out, and initial PAM authentication has been started.

Monty Taylor reports RIP: errmsg.sys, in its place is gettext which is a standard for outputting strings.

Comparing drizzle …