Oracle ATG Web Commerce Search supports two types of paging, normal paging and fast paging. The key differences between them relate to the information you get back from the search engine about the number of pages of results, and the navigation you can build into your pages:
Normal paging is the default. In this mode, the search engine returns (in the form handler’s
pagesAvailableproperty) the total number of pages of results. You can create links that enable the customer to go directly to any page.Fast paging is specified by setting the
fastPagingproperty of the search request totrue. In this mode, the search engine does not return information about the total number of pages of results;pagesAvailableis set to the highest-numbered page that has been rendered so far. You can enable customers to go to the next page or to any page previously rendered.
For a single-partition index, normal paging is always enabled (the fastPaging property is ignored). For a multi-partition index, you can choose between normal paging and fast paging, but fast paging is recommended. Fast paging is much less resource-intensive than normal paging. On multi-partition indexes, normal paging can be very memory- and CPU-intensive, because results from the partitions must be merged.
