[Ruby] How to patch ruby-mysql bindings?

[James Moore]

If you're having serious performance problems, I'd consider not using
ActiveRecord at all - it's not the first tool I'd use for bulk data
transforms.  Having said that, it's probably good enough for lots of
applications, and a couple million inserts shouldn't be a big deal.

But I'm with Ryan - this isn't something I'd tweak until I knew it was the
problem.  And if I knew ActiveRecord was the issue, I'd be more inclined to
either a) bail on it completely, rather than try to tweak it, or b) figure
out how to divide up the problem so it could run on a couple machines in
parallel. 

Assuming that MySQL itself isn't the problem; with only a couple million
inserts+updates/day, it's very unlikely that you're going to hit issues with
the database itself handing the load, unless you're running it on completely
gutless hardware.

(You aren't by any chance running without caching turned on?  ActiveRecord
will continually ask the database for info about what the tables look like
if it's not in production mode, and this will obviously rip the heart out of
your performance levels.)

 - James Moore

> -----Original Message-----
> From: ruby-bounces at zenspider.com [mailto:ruby-bounces at zenspider.com] On
> Behalf Of Dan Harms
> Sent: Monday, October 16, 2006 12:34 PM
> To: Seattle Ruby Brigade!
> Subject: Re: [Ruby] How to patch ruby-mysql bindings?
> 
> Fair enough.  No, I haven't measured any bottlenecks yet.  I am
> working on an application that is importing over 500K records daily
> with multiple updates per record, and thought this might be a
> pre-emptive attack on my part.  I'll get some more specific numbers to
> benchmark against.
> 
> Is patching the bindings generally not recommended, or just time
> intensive, so not worth it unless absolutely necessary?
>