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]
