Intro
The first working version (0.4.3) of SIGAR I_S plugin is now
available on Launchpad. You are welcome to download and give it a
try:
bzr branch lp:~m.ch/mysql-server/sigar-plugin
As this product is still in development stage you probably don't
want to install it on you production server. I'd rather suggest
to play with it on some non-important MySQL server
instance.
So what actually this plugin does. It uses Hyperix SIGAR library
to gather and analyze operating system information. As SIGAR
library is OS independent we can gather information on different
unix platforms as well as on Windows family OS.
What this plugin is not. It's not a way to start or stop OS
services, interrupt its work or affect it in any way.
Features
1. You don't need to install or compile SIGAR library yourself as
the source files come already with SIGAR files …
my “mysql client fixes” branch on launchpad contains fixes for eleven bugs (nine of them reported on bugs.mysql.com).
don’t get too excited — these are all the lowest priority-level bugs, mostly typos in comments and documentation.
now i have to figure out the latest process for actually getting these changes into the official tree. there are different policies around how and when to push to trees since i was last doing any server development. from someone who is partially outside, it all seems very tedious and designed to make it impossible to fix anything. process gone bad.
the mysql server isn’t going to get the benefits of using a good, …
[Read more]..aka how to spend a magnificent Sunday-Monday in SUN’s company :)
If your applications run on Windows™ and you need a MySQL™ Cluster for testing purposes you can use Virtual Box to install SUN Solaris™ 10 and set up the Database Cluster creating 4 Solaris™ Zones (4 IP are required for a minimal Cluster setup).
It’s an interesting scenario.
You will need:
You can create the Solaris™ Zones manually or you can create them …
[Read more]
As the years go by, data pages on disk have to get bigger. 16 KB
pages were good for databases in the late 1990's, but today's
data pages should probably be 64 KB. Page sizes go up over time
because memory gets cheaper, and disks get much larger, but disks
do not get very much faster.
In 1997, a Megabyte of memory cost $15, but today it costs 10
cents. A new SCSI drive held 4 GB then but 146 GB today. If cost
is held constant, today's machine has 150 times the memory and 36
times the storage of a machine from ten years ago, but the
performance of disks is only about 3 times better. Disks
are still about 3 inches across and turn at about 10K RPM;
today's best disk might deliver about 180 I/Os per second (IOPS),
compared to 60 IOPS in 1997. And since the disk doesn't move much
faster, it makes sense -- given the cheap storage both on disk
and off -- to transfer a bigger chunk of data back and forth with
every disk access.
…
The evening plans didn’t wait for talks to be done. The IRC channel (#oscon on irc.freenode.net) was alive with talk of prospects for dinner and drinks after the conference. I myself was torn between a group going out for Lebanese and another going to Henry’s, but opted to go with my buddies from home to Henry’s.
It was worth it. If you haven’t been, Henry’s Tavern boasts 100 beers and hard ciders on tap (oddly, the beer list is the only menu *not* online - guess it changes too frequently). There are a ton of local beers that you can’t even get on the east coast just waiting for you to try, but there are also some rare treats, like the Belgian Lambic beers, which you don’t often see on tap. The food is a little pricey, but is really good, and the staff is very friendly. A couple of us …
[Read more]KEY ACCOMPLISHMENTS LAST WEEK
- Read the book "Data Mining: Practical Machine Learning Tools and Techniques" to learn about features of Weka.
- Played with Weka to analyze and visualize MySQL runtime data.
- As part of the effort to use push-build and Bazaar with Skoll, found a method to set $PATH in Skoll Client. Now, commands and executables in "non-standard" locations can be specified for Skoll Client (in this case bzr).
KEY TASKS THAT STALLED LAST WEEK
- Could not test or collect runtime data with Skoll Client due to Bazaar switch.
KEY CONCERNS
- None
TASKS IN THE UPCOMING WEEK
- Continue to research tools and methods to analyze runtime information.
- Runtime data collection.
A few days ago I reported on a problem with savepoints, but all
that it appeared to be was an extemporaneous warning message.
Well, I just found out that InnoDB can actually lose the
savepoints! The overall transaction can still be rolled back
successfully, but the savepoints themselves are completely gone.
This only occurs after the warning: "Got error 153 from storage
engine" happens twice in one transaction (if it only happens
once, the savepoints still work) which requires that alternating
savepoints be set 6 times. See the full report here: http://bugs.mysql.com/bug.php?id=38187.
Related to my post earlier today about the use of MySQL 5.0 and
the Open Query course on upgrading and new features... I thought
it might be good to do a broader poll of the MySQL population and
see what version people are using for development (not
deployment) right now!
Use this link to go directly to this OQ Poll page: Which MySQL version do you use for
development?
Development is not quite the same as production. It can be good
to use a newer version in development, as you have new features
(and fewer old bugs ;-) at your disposal. Regardless of the
release status of a version, by the time your application reaches
production stage, you will be comfortable with that version so
deploying on it will be fine.
Development is the ideal time for being …
| Leveraging Replication to Optimize MySQL Backup & Disaster Recovery |
| In a global market, the uptime and performance of your MySQL database is critical. Taking the database offline to perform backups is simply not an option, but using replication is not a backup solution. So, how do you backup your data with minimal impact to your production environment? Using the ZRM for MySQL in conjunction with your replication slave, the ZRM for MySQL can back up your environment with no impact to production. |
Outline:
|
MySQL 5.1 is nearly GA (not debating that fun now ;-), MySQL 6.0
has interesting new magic such as Falcon and online backup. But I
still have many clients that are on MySQL 4.0 or 4.1 both in
production and development. Works fine, overall, but quite a few
problems would be nonexistent if they were on 5.0, and by making
use of some changed or new features various aspects could be
faster.
The Open Query MySQL 5.0 Upgrade and Advanced Features course
day is for this group of developers and DBAs, but also for users
moving to MySQL and going straight for MySQL 5.0 (as they should,
please don't *start* with earlier versions!).
We delve into the differences and new features. This includes
- Views — did you know they're updatable, and have you considered using them for smart access control? (tables, columns, rows) …