From: Christian Neukirchen <chneukirchen@...>
Date: 2005-11-29T02:58:10+09:00
Subject: Re: building ruby for speed: wise or otherwise?

Hugh Sasse <hgs@dmu.ac.uk> writes:

> On Tue, 29 Nov 2005, Robert Klemme wrote:
>
>> If Hugh is using ActiveRecord intensively with a database then it's most
>> likely that he'll see no positiv performance effect from compiling it with
>> more aggressive optimization.
>> 
>> In fact it's likely that careful optimization on the database side will
>> yield better results.  This can be as easy as creating some indexes - but
>> might be much more complicated - depending on the bottleneck.  (Often it's
>> IO and this might have several reasons, from sub optimal execution plans
>> to slow disks / controllers.)
>> 
> At the moment my script to populate the tables is taking about an
> hour.  Anyway it's mostly ruby I think, because it spends most of
> the time setting up the arrays before it populates the db with them.

Do you use transactions correctly?

> Besides that, I'm fairly new to database work, so I'm trying to
> optimize what I know about before I start fiddling with the db.
>
> Slow disks/controllers (+ lots of users) could be a factor, the
> machine is 5.5 years old.
>
> But those are good points. Thank you.        
>         Hugh
-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org