Regardless of what database you use (MS-SQL, Oracle, Postgres, MysQL-InnoDB, etc..), there's a lot of overhead in implementing ACID properties in a RDBMS, especially when disks are involved, which means queries are going to block. For databases that aren't ACID-compliant (like MySQL-MyISAM), that overhead doesn't exist, but reading threads block on the writing threads.
+Regardless of what database you use (MS-SQL, Oracle, Postgres, MySQL-InnoDB, etc..), there's a lot of overhead in implementing ACID properties in a RDBMS, especially when disks are involved, which means queries are going to block. For databases that aren't ACID-compliant (like MySQL-MyISAM), that overhead doesn't exist, but reading threads block on the writing threads.
never blocks. See the "Is memcached fast?" question below.
@@ -77,5 +77,5 @@ they'll eventually consume all your resources. You'll find yourself adding replicated slaves at an ever-increasing rate to make up for the -diminishing returns each addition slave provides. +diminishing returns each additional slave provides.The next logical step is to horizontally partition your dataset