|Bookshelf Home | Contents | Index | PDF|
To maximize the cache hit rate (and hence, performance and scalability), partition the transform search specification into a high selectivity clause that is executed by the database and used as part of the PSP cache key (the Search Specification input argument) and a low selectivity clause that is executed by the PSP transform itself to further filter the query results (the In Memory Search Specification input argument). When you use the In Memory Search Specification input argument in combination with a Search Specification input argument, your search specification is, effectively,
The order of search implementation is as follows: first the Search Specification input argument is applied to the database query. Next, the returned result set is further filtered in memory by applying the In Memory Search Specification input argument.
Example values for Search Specification and In Memory Search Specification are shown in Table 24 for the Pricer Simple Volume Discount step.
The example shown in Table 24 results in one query for each volume discount that retrieves all result rows. All subsequent queries against that volume discount are served from the cache regardless of the values for [Extend Quantity Requested] or Timestamp().
NOTE: In Memory Search Specification execution does not use sophisticated database features such as indexes. Make sure the result set searched in memory is not too large. For example, loading an entire price list in one query is not likely to improve performance; search a subset of the price list.
For information about PSP Cache performance, see About PSP Cache Performance Statistics.
|Siebel Order Management Infrastructure Guide||Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.|