If you have reason to think that Oracle ATG Web Commerce Search is underestimating the size of your index, you can manually adjust the size of physical partitions.

For example, estimation says that your content requires three physical partitions, but you know that you are very close to needing four. To rule out any potential performance problems, you overrule the estimation and create four partitions instead. If this happens often, you may want to adjust the fullnessOfRecommendedPartitions setting in the /atg/search/routing/Configuration.properties file to some number less than one, as shown:

fullnessOfRecommendedPartitions=0.7

Going forward, Search will estimate your content based on 70% of the maximum physical partition size, making it less likely that your partition will fill up.

To adjust the partition size, change the MemoryReserveSize property in the AEConfig.xml file. This setting controls how large a partition can be. For 32-bit Windows, the default setting is 0x54000000 (1.4 GB); 64-bit systems default to as much physical memory as possible.