The use case is be
Base [abstract @Entity, joined inheritance]

• SmallEntity1 [@Entity]
• SmallEntity2 [@Entity]
• (...)
• SmallEntity20 [@Entity]
• Document [abstract @Entity, joined inheritance]
  • Document 1 [@Entity]
  • Document 2 [@Entity]
  • Document 3 [@Entity]

We're dealing with a large inheritance structure, causing the root entity cache to be more than one gigabyte in large applications, but about 80% of the cache consists of documents. So for this scenario, It would be nice to have two caches (two threads)

• one for all documents
• one for all small entities

From what I see, this also fits to the "entire hierarchy stored in the same place" premise?