Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of clamey@localmatters.com
 designates 216.241.189.144 as permitted sender)
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Tue, 22 Jul 2008 16:32:08 -0600
Subject: Re: ibatis+springframework for millions data loading
From: Christopher Lamey <clamey@localmatters.com>
To: <user-java@ibatis.apache.org>
Message-ID: <C4ABBC08.B3B8%clamey@localmatters.com>
Thread-Topic: ibatis+springframework for millions data loading
Thread-Index: AcjsSsZgBQNTtlg+Ed2nTAAbY5caEQ==
In-Reply-To: <16178eb10807221524w562e2f8ev1420a1a5c2eff940@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

On 7/22/08 4:24 PM, "Clinton Begin" <clinton.begin@gmail.com> wrote:

> True, other tools may be better...
> 
> But with a RowHandler, iBATIS could easily meet this requirement.  I've used
> iBATIS RowHandlers for ETL type stuff and achieved crazy performance with
> batch updates.  15,000 records per second on the Netflix prize data.

Definitely, I've used rowhandlers in iBATIS for similar stuff with millions
of rows as well.  Complicated data transforms or the lack of ability to do
command line stuff for various reasons have usually been why I've gone with
a RowHandler.

But if I'm just copying data from database a to database b and I don't need
complicated transformations or handling, I've never seen anything faster
than the database's native bulk loaders (sqlldr, bc, copy, etc.)

Cheers,
Chris