I’m pleased to announce the initial list of keynote speakers for the Percona Live MySQL Conference & Expo, April 22-25 in Santa Clara, California. The conference promises great content with over 90 speakers in more than 110 sessions, 15 tutorials, and multiple keynotes. The MySQL Community Awards 2013 are also now accepting nominations.
FOSDEM 2013The Free and Open source Software Developers’ European Meeting (FOSDEM) is a two-day event organized by volunteers to promote the widespread use of Free and Open Source software. As in previous years, there is a dedicated stream of MySQL Sessions.
I’ll be presenting a webinar next Wednesday, January 23, about issues application developers should think about for scaling out read-query traffic using multiple MySQL instances in a replication pair.
Specifically, about the care we have to take because replication is asynchronous. This means the slave may not have current data at all times, so an application must choose to query the slave or the master dynamically. As much as possible, we’d like to automate this choice so that application developers can be the most productive.
Here are three security tasks I handled, which I'm happy to say were easily solved with common_schema's views and routines (with no prior planning). Two are so easy, that I actually now integrated them into common_schema 1.3:
Queries in MySQL, Sphinx and many other database or search engines are typically single-threaded. That is when you issue a single query on your brand new r910 with 32 CPU cores and 16 disks, the maximum that is going to be used to process this query at any given point is 1 CPU core and 1 disk. In fact, only one or the other.
One of the most common causes of a poor Sphinx search performance I find our customers face is misuse of search filters. In this article I will cover how Sphinx attributes (which are normally used for filtering) work, when they are a good idea to use and what to do when they are not, but you still want to take advantage of otherwise superb Sphinx performance.