[Ruby] Parallel migration

[James Moore]

Think bigger.  Most people run heavier hardware when they've got large
databases.  You've got stripes across multiple drives, tables on different
drives, etc - all the fun toys for modern databases.  Depends on what you're
doing and what your database software supports.  If you only have one drive
to talk to, throwing more writes at it can maybe be a win depending on how
smart its controller is and what sort of processing you're doing.

Even a tiny mysql installation can do simple things like put two
heavily-used tables on two different drives, and presumably postgres has
similar cheap-and-cheerful tricks that are almost free.

- James

> -----Original Message-----
> From: ruby-bounces at zenspider.com [mailto:ruby-bounces at zenspider.com] On
> Behalf Of Michael Kreeger
> Sent: Friday, January 19, 2007 12:23 PM
> To: Seattle Ruby Brigade!
> Subject: Re: [Ruby] Parallel migration
> 
> Sounds like your going to be limited to the speed of the disk.
> Parallel procs are great for number crunching but databases funnel
> down to one table for writing otherwise there would be conflicts.
> 
> Am I thinking about this the right way?  Anyone?
> 
> Michael