Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Tue, 29 Nov 2005 16:29:11 +0100
From: Lars Clausen <lc@statsbiblioteket.dk>
Subject: Re: Workarounds for too many open files?
In-reply-to: <200511280817.21648.msegel@segel.com>
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <1133278151.31586.422.camel@pc977.sb.statsbiblioteket.dk>
Organization: Statsbiblioteket
MIME-version: 1.0
Content-type: text/plain
Content-transfer-encoding: 7BIT
References: <1132906493.13290.122.camel@pc977.sb.statsbiblioteket.dk>
 <1133172624.31586.33.camel@pc977.sb.statsbiblioteket.dk>
 <200511280817.21648.msegel@segel.com>

On Mon, 2005-11-28 at 15:17, Michael Segel wrote:
> On Monday 28 November 2005 04:10, Lars Clausen wrote:
> 
> I guess anyone who's going to try and create a 100GB database will also run in 
> to this problem. (Remember the discussions on scalability?)
> 
> Since I haven't seen the code on how Derby stores data to the disk, why so 
> many files per index?
> 
> A possible, but ugly work around is to create the index as you load the table.
> (Ugly in that you'll take a performance hit. However, this should work.)

That's what I did first, later I split it into two to see why it
crashed.

-Lars