[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-469) Filter caching using causes excessive memory use

Filter caching using causes excessive memory use ------------------------------------------------ Key: HSEARCH-469 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-469 Project: Hibernate Search Issue Type: Improvement Components: query Affects Versions: 3.1.1.GA, 3.2.0.Beta1, 3.2.0.CR1 Environment: hibernate-core-3.3.2.GA Reporter: Dobes Vandermeer Assignee: Sanne Grinovero The CachingWrapperFilter uses the reader instance (CacheableMultiReader) as a key for the caching. However, the reader instance keeps pointers to byte arrays in its "normsCache" and in the "normsCache" of its sub-readers; each array has one byte for each document in the index and in some cases there will be multiple of these arrays associated with differet fields. For an index with millions of records this can result in an apparent "leak" of hundreds of megabytes of memory as those readers are not re-used and the MRU cache used by default will keep up to 128 hard references to the readers by default. The search system must either re-use or delete the normsCache, OR the cache key for these filters should be tied to something else that doesn't keep references to potentially huge data arrays. Otherwise the scalability of the search subsystem is significantly impacted when using filters, as you must have enough heap to accommodate up to 128 times as many copies of the norms arrays.