I have just accepted a position with Lycos as Principle Software Engineer, which I'm very excited about and will write about in a later post on this blog.

More immediate is the need to find someone to replace me at Grazr. I want to find them a well-qualified person. Some of the requirements are:

5+ Years with:

* Perl, mod_perl development, Perl OO, DBI
* Developing web applications with MySQL
* SQL -- and this means more than 'select * from foo'
* MySQL Administration
* Knowledge of good schema design
* Apache
* Linux Administration

Other needs:

* Sphinx Search Engine
* Memcached
* Familiarity with Nagios
* Understand different MySQL storage engines
* Familiarity with MySQL UDFs (I have a few I wrote at Grazr that someone will have to figure out)
* Any other MySQL monitoring tools (Cacti, etc)
…

As Lehman Brothers files for bankruptcy, investment banks and brokers using its technology are in the dark about the future of their investments READ MORE

I just got back from vacation and noticed that two patchsets have been released that greatly improve Innodb performance! Maybe I need to take more breaks

Yasufumi Kinoshita's patches Percona recently released a patch which includes performance fixes developed by Yasufumi Kinoshita from NTT Comware. This helps diskbound applications quite significantly. Details at Bug #29413 Maximum performance of OLTP benchmark is not so scalable on multi-cpu. It looks like the bulk of performance improvements come from breaking up the lock guarding the buffer pool structures, and improvements in the IO code path. The "buf_pool->mutex" also gets quite hot when concurrency is not limited (via innodb_thread_concurrency) and …

I just got back from vacation and noticed that two patchsets have been released that greatly improve Innodb performance! Maybe I need to take more breaks

Yasufumi Kinoshita's patches Percona recently released a patch which includes performance fixes developed by Yasufumi Kinoshita from NTT Comware. This helps diskbound applications quite significantly. Details at Bug #29413 Maximum performance of OLTP benchmark is not so scalable on multi-cpu. It looks like the bulk of performance improvements come from breaking up the lock guarding the buffer pool structures, and improvements in the IO code path. The "buf_pool->mutex" also gets quite hot when concurrency is not limited (via innodb_thread_concurrency) and …

Last week Kenai went beta, with the usual services in a development hub site plus an additional "connected" angle. Our GF CORBA project is already using its Hg repository but another very interesting angle is the technology mix.

Here's a wakeup call to all the good folks on planet MySQL :

Denver Post: Gone: Comments...


Today's a great day to:

1) Review your backup logs.
2) Perform a recovery drill on a development server.
3) Validate the backed up data by running checksums, comparing tables or file sizes, etc.

Here's a wakeup call to all the good folks on planet MySQL :

Denver Post: Gone: Comments...


Today's a great day to:

1) Review your backup logs.
2) Perform a recovery drill on a development server.
3) Validate the backed up data by running checksums, comparing tables or file sizes, etc.

Suppose I have around 30 servers with MySQL 4.1 each with up to 1Tb of MyISAM tables. We need to upgrade their OS to support new hardware. We want to upgrade to 64-bit architecture to use the hardware efficiently.

Upgrading to 5.x seems like a good idea, as the additional validation work will be the same as would have to be done anyway - so we could effectively upgrade our MySQL version "for free", i.e. no additional QA work would be required than would be needed anyway.

Upgrading at any other time would involve a repetition of the validation exercise, which is not trivial as we must test at least:

• All features of the complex application which use these databases still work without errors
  
• The behaviour of the new version is consistent with the old one (e.g. results returned)
• Performance needs to be measured to ensure that performance regressions haven't happened (or …

»XAMPP kompakt« aus dem Bomots-Verlag war das erste Buch, das sich ausschließlich mit XAMPP beschäftigt und Einsteigern einen ersten umfassenden Blick in die Webserver-Welt geboten hat.

Jetzt ist es in einer aktualisierten und erweiterten Neuauflage erschienen und der Autor Holger Reibold war so freundlich uns ein paar Belegexemplare zur Verfügung zu stellen.

Diese wollen wir natürlich nicht nur für uns behalten und verlosen daher 10 dieser Exemplare unter allen interessierten XAMPP-Nutzern.

Als kleines Bonbon gibt es für die ersten drei Plätze auch noch jeweils eines unserer überaus begehrten XAMPP-T-Shirts mit dem AMPP-Motiv auf der Rückseite.

Zum »XAMPP kompakt«-Preisausschreiben

Seriously kids, what’s with the lack of scalability? I’ve never seen CNN or the NYTimes go down on “trimmed” versions.

Is it a question of bandwidth? Is it lack of hardware?

Take for example, Malaysiakini (the first alternative news source in Malaysia, with a subscription model built around it). It runs FreeBSD, uses PostgreSQL, and has a CMS on top of it (so almost a LAMP stack right there). There’s even use of Squid for caching. Yet there’s lacking load balancing? This is where the cloud can come into play, when there’s high traffic.

Next up, …