Guillermo Averboch <[EMAIL PROTECTED]> writes: > Hi, I'm a fairly new Derby user, and I can't seem to find the answer to this > question anywhere: How does derby.storage.pageCacheSize work when the same > process has several opened Derby databases at the same time? > > According to the Derby documentation, derby.storage.pageCacheSize is system- > wide, hence individual databases cannot set their own value for it. Does this > mean that there is only one cache, which is shared by all databases, or that > Derby creates separate caches for each database, each of which can grow up to > the size specified by derby.storage.pageCacheSize?
Hi Guillermo, It's the latter; each database has its own page cache, and each cache can hold up to derby.storage.pageCacheSize pages. -- Knut Anders
