The number of changed items accumulating in the queue can vary greatly, depending on how frequently your data changes and how long you specify between incremental updates. Rather than processing all of the changes at once, the IndexingOutputConfig component groups changes in batches called generations.

The EndecaIndexingOutputConfig class has a maxIncrementalUpdatesPerGeneration property that specifies the maximum number of changes that can be assigned to a generation. By default, this value is 1000, but you can change this value if necessary. Larger generations require more ATG platform resources to process, but reduce the number of Endeca jobs required (and hence the overhead associated with starting up and completing these jobs). Smaller generations require fewer ATG platform resources, but increase the number of Endeca jobs.

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved.

Legal Notices