The MySQL proxy got some final touches to make it ready for the first release:

• a command-line interface
• some more mode descriptions for the different modes of operation

You can choose between three modes for now:

• pseudo server
• injection proxy

• replication client

For the future we plan:

• connection pooling

• replication filtering and off-loading

The options so far:

$ mysql-proxy --help
  --listen-port=<port>                  port the pseudo mysql-server should listen on in server-mode (default: 4040)
  --server-port=<port>                  port of the remote mysql-server in proxy- and reverse-mode (default: 3306)
  --server-ip=<ip>                      ip-address of the remote mysql-server in proxy- and reverse-mode (default: 127.0.0.1) …

One of the projects I am looking at right now is performance on eight
proc (2 proc/4core) machines that Intel is providing.

An interesting situation I've noticed is the behavior in Innodb in
regards to Innodb and primary key INSERTS. From observing behavior
with GUID vs Autoincrement, Innodb runs into issues around ~75
concurrent acting connections (aka not idle). GUID size aside, using
a different key then an Autoincrement seems to help with scaling
Innodb on multiple CPU's (looking at this with a 4proc machine shows
that this issue show up at a later scaling point).

None of the other MySQL/3rd party engines behaved this way in
testing, so it looks to be a localized problem in Innodb. Blackhole
just gives you a base cost for an INSERT statement with no disk IO.

The test used 100K of rows and inserted them by splitting them across
…

Oh, MySQL. That little database that just isn't quite as good as the Big Important Proprietary Incumbents....

Except that, apparently, enterprises aren't getting this message. In fact, 40% of them strongly disagree with the feeling above, as Stephen Shankland reports:

You now can discard any lingering traces of doubt that the open-source MySQL database competes with the incumbent proprietary products from Oracle, Microsoft and IBM.

Data released Thursday from an Evans Data Group survey of database usage among developers shows MySQL use increased from 32 percent in 2004 to 40 percent last year. The survey tallied real production use in corporate environments, not just tire-kicking or pilot projects

Reality bites if you're DB2 or Oracle. Because while I would think much of MySQL's gains are coming at the expense of no one (meaning, MySQL is …

Working with various projects using MySQL I observe a lot of problems are coming from very simple fact - product is designed containing features which developers do not know how to implement effectively.

In many companies you would see "waterfall" like approach for web application development at least on business-development boundary. Business people would dream up some features for developers to implement which developers simply take and implement as good as they can - unfortunately often not good enough to match performance and scalability requirements for the application.

In the end such approach may have nasty surprises - application gets serve performance problems due to features which might be not critical after all and even Business people would rather make things running fast than having these features working exactly as required.

So what is my point ? Only plan for features which you know how to …

MySQL Table Maintainer is a new utility to help you run table maintenance commands (ANALYZE, CHECK, OPTIMIZE, REPAIR) on your MySQL tables. It's part of the MySQL toolkit.

I've just released updates to all the tools in the MySQL Toolkit. The biggest change I made to most packages is using DBD to read MySQL's option files, though some packages got more significant updates.

I have downloaded the source for the latest SolidDB engine for MySQL and modified it to compile on Mac OS X PPC operating system. There were no new changes in my modification process, so any differences are specific to the engine and will be bug fixes and new features.

Currently I am running the mysql-test set on the new engine and modifying some of the tests to formulate a test base for newer versions of the SolidDB engine as it is released.

I have made a precompiled binary available for version v0064.
SolidMySQL for Mac OS X (PPC)

Please email me at info@cybersite.com.au if you have any problems with the binaries running. If you have issues with the storage engine itself, p

read more

I have downloaded the source for the latest SolidDB engine for MySQL and modified it to compile on Mac OS X PPC operating system. There were no new changes in my modification process, so any differences are specific to the engine and will be bug fixes and new features.

Currently I am running the mysql-test set on the new engine and modifying some of the tests to formulate a test base for newer versions of the SolidDB engine as it is released.

I have made a precompiled binary available for version v0064.
SolidMySQL for Mac OS X (PPC)

Please email me at info@cybersite.com.au if you have any problems with the binaries running. If you have issues with the storage engine itself, p

read more

Over the last weeks I wrote a mysql-proxy which changes the way you operate with the MySQL Server.

A proxy can operate as Man in the Middle and pass through to network packets to the MySQL Server, but it also change the packets when needed. This opens the several possibilities like a

• pseudo server done
• injection proxy done
• load-balancing proxy done
• connection pool
• XA Transaction Manager
• replication client
• replication filter
• replication off-loader

Some of them are already implemented, some are only ideas for the future.

• http://forge.mysql.com/wiki/MySQL_Proxy has the source and the binaries
• …

The MySQL proxy got some final touches to make it ready for the first release:

• a command-line interface
• some more mode descriptions for the different modes of operation

You can choose between three modes for now:

• pseudo server
• injection proxy

* replication client

For the future we plan:

• connection pooling

* replication filtering and off-loading

The options so far:

$ mysql-proxy --help
  --listen-port=<port>                  port the pseudo mysql-server should listen on in server-mode (default: 4040)
  --server-port=<port>                  port of the remote mysql-server in proxy- and reverse-mode (default: 3306)
  --server-ip=<ip>                      ip-address of the remote mysql-server in proxy- and reverse-mode (default: 127.0.0.1)
  --replication-user=<user>             user-account …