From: "Jonathan <zjll9@...> <zjll9@...>" <zjll9@...>
Date: 2005-11-29T06:14:06+09:00
Subject: Re: building ruby for speed: wise or otherwise?

hgs wrote:
> On Tue, 29 Nov 2005, Christian Neukirchen wrote:
> 
>> > I've only got one process accessing the db at the moment.  If you've
>> > got pointers on common errors, misconceptions, etc I'd be glad to
>> > learn about them.   So I suppose that answer is likely to be "no"
>> > :-)
>> 
>> If you need to INSERT bigger chunks of data, put it in an transaction
>> so it will write the data to disk only once.  If you need to insert
>> even bigger amounts of data, using COPY (usage depends on your
>> database) can speed things up a lot too.  It may be helpful to add
>> indexes after importing the data.
> 
> OK, thanks.
>> 
>         Hugh

Temporarily disabling constraints (UNIQUE and FOREIGN_KEY) will improve 
performance too if you are sure the data is safe.


-- 
Posted via http://www.ruby-forum.com/.