Production databases on SSDs?

[James Laver]

On Tue, Nov 10, 2009 at 5:46 PM, Richard Huxton <dev at archonet.com> wrote:
>
> * - it's not the transaction logs themselves that are the problem so
> much as having constant small writes to them causing the disk heads to
> seek back and fore. This is why you tend to put them on their own disks.

Or play other fun tricks, like only partitioning 25% of the disk and
leaving the rest to waste, so it's using the fastest 25% of the disk.

On a WD VelociRaptor[1], it could be extra awesome.

--James

[1] Yes, the name sucks. Apparently they wanted to fit 'raptor' in so
people would know it's an evolution of the raptor.