Landmark transaction and query paging

A Landmark query can return any number of records. The loop gets executed for each record. When the Landmark node is executed initially, it retrieves a set of records, which will be a maximum specified by the page size parameter. The iteration loop occurs for every record retrieved. After looping through all the records in the set, it then retrieves an additional set of records which iterates through the loop until all records have been retrieved. The Landmark node always retrieves all records specified by the query. However, the page size parameter controls whether all records are retrieved in a single set or whether several smaller sets are retrieved. Either way, the same total number of records is processed.

The page size parameter affects the amount of memory used. The larger the setting, the more records that are in memory at a time. Depending on your system and the number of records that need to be retrieved, setting the parameter very high might not be a good idea. Conversely, a small page size setting means the loop has to return to the server more times to fetch records which could slow down loop processing time.

The page size parameter can be changed at any time. For example, you found that a process was running slow and your system administrator was able to isolate the problem to execution time for the Landmark Transaction node. You could change the page size parameter to retrieve more records in the fetch to see if that fixed the problem.