A few users have reported that their comments are randomly not showing up on the site. We can’t find them in the database; they aren’t getting put into the spam queue, etc. I just got another report of this and found the INSERT for the comment in the database’s binary log. Of course, the comment is not in the database, as usual. I’m looking into this now.
Is this an amazing new feature or the next step after the change to bugs.mysql.com? I was about to file a bug report to improve the MySQL manual, but that won't happen now:
We just pushed to sysbench support for workload against multiple tables ( traditionally it used only single table).
It is available from launchpad source tree
This is set of LUA scripts for sysbench 0.5 ( it supports scripting), and it works following way:
- you should use
--test=tests/db/oltp.lua to run OLTP test
./sysbench --test=tests/db/oltp.lua --oltp-tables-count=25 prepare
Percona Server Percona Server 5.5.11-20.2 is now available for download, including an experimental build for MacOS.
Released on April 28, 2011, it is the current stable release in the the 5.5 series.
The following quotes are the first sentences in the replication chapter of two similar books. Both are admin cookbooks. One is for PostgreSQL, one for MySQL.
Replication isn't magic, though it can be pretty cool. It's even cooler when it works, and that's what this chapter is all about.
Warning — for testing purposes only!
Oracle Technology Network (OTN) Developer Day for MySQL will take place on May 3rd in Santa Clara, CA to help DBAs and Developers get started and get better with MySQL. In this free, one-day event, we will cover topics from database design, application development, to MySQL administration and management. You'll also learn the guidelines and best practices in performance tuning and scalability.
Attend this event and gain the knowledge to:
• Develop your new applications cost-effectively using MySQL
• Improve performance of your existing MySQL databases
There are many ways to slice and aggregate metrics of activity on a system such as MySQL. In the best case, we want to know everything about the system’s activity: we want to know how many things happened, how big they were, and how long they took. We want to know precisely when they happened. We want to know resource consumption, instantaneous status snapshots, and wait analysis and graphs. These things can be expensive to measure, and even more importantly, they can require a lot of work to analyze.