Navigation

Changeset 794 for trunk

Timestamp:

09/08/08 00:21:11 (4 months ago)

Author:

dormando

Message:

Fix typos on site.

Pointed out by:
John Rockefeller <jrockefeller1@gmail.com>

Files:

r478	r794
36	36
37	37	<?h1 Shouldn't the database do this? h1?>
38		<p>Regardless of what database you use (MS-SQL, Oracle, Postgres, MysQL-InnoDB, etc..), there's a lot of overhead in implementing <a href="http://www.wikipedia.org/wiki/ACID">ACID</a> 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.</p>
	38	<p>Regardless of what database you use (MS-SQL, Oracle, Postgres, MySQL-InnoDB, etc..), there's a lot of overhead in implementing <a href="http://www.wikipedia.org/wiki/ACID">ACID</a> 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.</p>
39	39	<p><?memd?> never blocks. See the "Is memcached fast?" question below.</p>
40	40
…	…
77	77	they'll eventually consume all your resources. You'll find yourself
78	78	adding replicated slaves at an ever-increasing rate to make up for the
79		diminishing returns each addition slave provides.</p>
	79	diminishing returns each additional slave provides.</p>
80	80
81	81	<p>The next logical step is to horizontally partition your dataset