Thank you for the reply. I think you're right that it has a lot to do with memory and the particular server/machine running it. There's at least a problem with the max number of files that can be open at any given time, since it seems to need to open a file descriptor for each collection. I'm not sure what the max is for any given OS, but that's probably the answer. My dev Linux box seems to max out at a ulimit on open files of 1048576, but I'm not sure where that number comes from.
Also, in my performance testing, I'm trying to create subcollections in a nested loop. Is there some reason why the subcollections are becoming corrupted this way? I'm closing the main collection before trying to open it and create a subcollection under it, but it doesn't seem to matter. BTW, this is all with the embedded version, in case it matters. -David On Wed, 10 Sep 2003, Vadim Gritsenko wrote: > David J. Thomson wrote: > > >Hello all, > > > >What is the maximum number of collections allowed? I read somewhere in the > >archives that ~1000 documents was the limit per collection from a > >performance standpoint, but any idea on the maximum number of collections? > > > > > > Collection stores list of sub collections in-memory, in the hash map. > So, one limiter will be memory. > Collection loads up list of sub collections on start-up. Another limiter > will be startup time. > > > >I'm thinking of needing a max of about 20,000,000, with relatively few > >documents in each, i.e. no where near 1000 per collection. Is that even in > >close? > > > > > > Try it and tell us. > > Vadim > > >
