Time left to the PHP 5.3 Release Party:

(JavaScript countdown - less than 48 hours…)

Time left to the PHP 5.3 Release Party:

(JavaScript countdown - less than 48 hours…)

I've been trading twitter responses back and forth with jswanhart of Kickfire recently on the state and planning of Views in Drizzle.

In Drizzle right now we do not have views. There are plans to add views which never "materialize", but that is still a couple of milestones off.

One of the problems when talking about views is that the word "materialize" has been over used.

To "materialize" a view, means that you take the view definition, turn it into a temporary table, and then join it against a query. In Drizzle we consider this a "no no".

Why? Because any query that does this is more then likely going to turn out to be to slow to be of any real use in our domain space. The same problem exists with subqueries though for the time being we are leaving them in. Subqueries at this …

I’ve written some new Nagios checks for MMM (MMM on Google Code … MMM on Launchpad). check_mmm is a part of http://code.google.com/p/check-mysql-all/, and is meant to be called locally on the MMM Monitor server (usually via NRPE). Feedback is welcome, usage is as follows: Usage: check_mmm --cluster C# Options: --cluster= The MMM Cluster to check [...]

Join the Sun and Kickfire team tomorrow to see the unveiling of the Kickfire’s On-Demand Trial. You can sign up for the live webinar and trial review here: http://tinyurl.com/kickfiretrial.

At Kickfire we’re very excited about this launch. We’ve had many customers who have asked for a quick way to trial the system to get a sense of the performance. In order to speed up setup time we are providing users with access to US Bureau of Transportation’s database. This database contains flight data from the last twenty years. The trial consists of four parts:

1) An overview of Kickfire and its technology (includes a short Flash movie)
2) An interactive tutorial of a couple of sample queries. The tutorial explains the DB schema, the SQL and the Kickfire features that get performance
3) A pick list of sample queries and comparison times against MySQL …

Recently with a client while running a number of disaster recovery tests I came across a nasty situation which was not part of the original plan and provided a far worse disaster situation then expected.

I should preface this condition with some of the environment conditions.

• MySQL 5.0 Enterprise 5.0.54
• RHEL 5 64bit
• Master and 2 Slaves
• MySQL Data and MySQL Binary Logs/MySQL Error Logs are on separate disk partitions

While running stress tests under high load, we tested the filling of partition containing the logs. This partition included the binary log and MySQL error log.

The observed output was.

• An error message was written to the MySQL error log. See below.
• Application throughput dropped, but did not stop.
• Binary logs stopped occuring.
• MySQL proactively stopped logging but continued to process …

Join the Sun and Kickfire team tomorrow to see the unveiling of the Kickfire's On-Demand Trial. You can sign up for the live webinar and trial review here: http://tinyurl.com/kickfiretrial.

At Kickfire we're very excited about this launch. We've had many customers who have asked for a quick way to trial the system to get a sense of the performance. In order to speed up setup time we are providing users with access to US Bureau of Transportation's database. This database contains flight data from the last twenty years. The trial consists of four parts:

1) An overview of Kickfire and its technology (includes a short Flash movie) 2) An interactive tutorial of a couple of sample queries. The tutorial explains the DB schema, the SQL and the Kickfire features that get performance 3) A pick list of sample queries and comparison times against MySQL running on commodity …

I know, I know, loads of people have been waiting for these…

So here we go, I’ve finally sorted a downloaded version of the Dojo examples from the presentation I provided at the MySQL Users Conference 2009.

There are three examples:

• The auto-paging table example, which uses the functionality of the Dojo Toolkit and the QueryReadStore to automatically load content from a table.
  
• The basic graphing example, which loads data dynamically and plots a graph.
  
• And the zooming version of the same basic graph interface

There’s a README in the download that contains instructions on getting everything up to speed, although it should be fairly obvious. It’s attached to the bottom of this post too.

Any questions for getting this to work, please go ahead and ask!

Download the package …

What if you could evaluate, deploy and maintain a Data Warehouse (DW) and Business Intelligence (BI) solution for up to 90% less than the cost of proprietary software? What if you can find a solution that has been adopted by customers in all industries and is technically sound and scalable?

You can, with open source Data Warehousing from MySQL and Business Intelligence from Pentaho.

Join this webcast to find out about real world BI/DW deployment strategies that that offer you robust capabilities, yet with a lower total cost of ownership (TCO).

The MySQL and Pentaho solution has been proven in diverse deployments, from small companies to large enterprises. The subscription support model aligns customer and vendor interests, lowering both your costs and project risks. Join this webcast and learn how to be successful in your BI/DW projects. We will show you how MySQL and Pentaho can easily provide a complete …

As I had written earlier in Understanding InnoDB MVCC, I am trying to understand why InnoDB is taking a lock on data during an UPDATE when I do not expect this to happen.

Not wanting to go looking at the InnoDB source code to understand the problem, I’m endeavouring to possibly use existing MySQL monitoring to try and understand the problem better. In this case, I’m going to investigate SHOW ENGINE INNODB STATUS first. An old but still relevant article for reference is SHOW INNODB STATUS walk through. The MySQL High Performance book is also a good starting reference.

I’ve just installed 5.1.36 on a new Linux 64 bit laptop for this test.

For now all I’ve done is ensure the innodb_buffer_pool_size is sufficient …