Lookup Transform Performance

Are there any considerations for the performance of large lookup tables? I am currently working on a new transform with ~1700 values.

From the lookup page:

SailPoint recommends keeping the table to be 100 entries or less. While there are technically no hard size constraints on the number of keys and values, the larger these objects are they more difficult to maintain and use, and larger tables can slow down transform fetching and calculation.

From Neil:

We have seen customers have a 1000 or more. Its not ideal, but it will work… slower.

1 Like