Matthew Toseland wrote: > After various reports of OOMs, and after high CPU usage which might have > been related to excessive GCing, I did some profiling. > > Having analysed the first 70% of memory on the dump, with a 100MB > overall limit, the Berkeley DB Java Edition that we use for the database > uses at least 54.5MB of RAM. databaseMaxMemory is not overridden in the > config, and therefore should be at the default value of 20MB. > > The documentation says: > "Note that the cache does not include transient objects created by the JE > library, such as cursors, locks and transactions." > > It is possible that the cache only refers to the first stack trace, > which is 17MB. However there are many other traces which appear to be > dealing with the database log (BDB is a log-structured database), many > of them rather large - for example the next 3 traces of 10MB, 5MB and > 5MB respectively. > > Any ideas? We can: > Have you talked to the BDB people about it? In my experience they have been very communicative and very helpful with such things even for projects not, you know, buying licenses. Even after Oracle bought them out they've been very helpful.
~Chris
