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)
From: Michael Segel <msegel@segel.com>
Organization: MSCC
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Workarounds for too many open files?
Date: Mon, 28 Nov 2005 08:17:21 -0600
User-Agent: KMail/1.8
References: <1132906493.13290.122.camel@pc977.sb.statsbiblioteket.dk>
 <1133172624.31586.33.camel@pc977.sb.statsbiblioteket.dk>
In-Reply-To: <1133172624.31586.33.camel@pc977.sb.statsbiblioteket.dk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200511280817.21648.msegel@segel.com>

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.)

-HTH...

>
> It turns out that this happens during index creation.  I was able to
> import the text file and run selects on it, but when I try to create an
> index:
>
> Derby creates files in the tmp directory at a rate of about 8 per
> second.  If it doesn't close all of these, it would run out of FDs
> (ulimit 1024) before long.
>
> I would file a bug report, but db.apache.org isn't responding.
>
> -Lars

-- 
Michael Segel
Principal 
MSCC
312 952- 8175 [M]