MySQL backups are essential to running a site with MySQL backend. Generally you can get away with doing nightly backups but on our site, due to couple issues we had in past, we are forced to do hourly backups of our db. Intially I was doing backup by using: mysqldump dbname > weekdayHour.dbname.sql hourly. [...]

MySQL AB today announced that OKQ8, Sweden?s largest gasoline vendor, will roll out a MySQL-based payment authorization and collection system during the first part of 2007.

Our sysadmin has a nice blog post with a few tips for using mysqldump, especially if your database is used for more than a basic site, or if you have stored procedures and/or triggers.

Problem:

One of the sites I maintain has been getting more and more traffic everyday. A very good thing for the site, not so good for the solo server which is serving those pages. The site is VERY dynamic with LAMP setup. We only have one server serving our web pages to our users. Since its a dynamic site with PHP and MySQL, it has a lot of load during peak times. Average load time of a page is between 1-2 secs during normal usage, 2-5 secs under average to heavy load.

During heavy load, we started to see our mysql stop responding to requests which is a big concern for us since we don’t show content if there is no db connection. We had to come with a solution, fast, to prevent this issue from appearing.

Solution:

So here are couple things I ended up doing on the server side to reduce load on this server without having to do much code change.

• We have couple other …

The Wall Street Journal and the San Francisco Chronicle have both written about how high tech companies in Silicon Valley are being much more frugal with investors' money than during the internet boom of the late 1990s.  Not surprisingly, just about every startup I know is using open source, whether it's well known companies like Digg, FaceBook, Linden Lab, or newer entrants like YouSendit, Soonr, …

Werner pointed us to Media Temple's entry on how to Scale MySQL in a large scale hosting environment. The short summary. Put them all in a virtual container and isolate them.

To make life a little easier at home and work I've put together a simple enough script that is run by cron to tally up statistics like: Innodb_data_reads, Innodb_data_writes, Qcache_hits, Qcache_inserts, Questions, Open_files and Open_tables over time (I sample every hour) with the ability to easily expand and add your own `show status` variables.

Next I'll create some nice graphical interface so it's more obvious how the server or cluster is running. You can grab the script over at my CV hosting. Note that actual client writes in a master master environment would be (writes / number of servers) roughly, very roughly. If you have any ideas for countering this please let me know.

Enjoy.
--
Copyright 2006-2008 Andrew Rose [rose.andrew@gmail.com] [andrewrose.co.uk]

I just learned from my colleagues in our Dublin office that Mårten Mickos, CEO of MySQL AB will be visiting them this coming weekend. They would like to take this opportunity to arrange a MySQL User Group Meeting, which will take place on Saturday, 27th of January, 18:00 o'clock in their offices:

MySQL Ireland,
Ground Floor, Misys Building,
Eastpoint Business Park,
Dublin 3
Ireland

This is your chance to meet and talk with Mårten and other MySQLers. There will also be free food and drinks and most likely a tech talk about MySQL (details will follow). So if you are located somewhere around Dublin, make sure to attend this event!

Thanks to MySQL, and in particular Jay, for giving me the opportunity to talk about PBXT at the up-coming MySQL Conference in April. I will be presenting a session with the title: PrimeBase XT: Design and implementation of a transactional storage engine.

Topics include the design of XT and how it differs from conventional implementations, experience with implementing storage engines, surprises and gotchas, and performance. So I think this talk will be of interest to both end-users and other developers of storage engines.

See you there!

If you ever get something like this:

bk clone -lq ndb bug25567

clone: unable to readlock /home/stewart/Documents/MySQL/5.1/ndb

then try this:

bk unlock -s

to remove stale locks.

I have no idea how anybody is meant to come to the command from the error message… blindly guessing ‘bk help unlock’ worked for me though.