Blogs

Default Search Results 100 or 300? in PeopleTools 8.60+

By Sathya Purusothaman posted 16 days ago

  

We recently upgraded from PeopleTools 859 to Tools 860. During the upgrade we observed that search results on the new classic search pages were showing the first 100 rows fetched by the search record. So we initially changed the configuration at global level to show 300 search results. 

This is from

Global Default rows in Search Results
But we were wondering why oracle has given default as 100 instead of 300. So we started looking into the new search page.  Then we decided to trace the PeopleCode from the point when the search button is clicked and see what the performance impact between 100 rows as default results and 300 rows as default results and below was our observation in some of the delivered pages in PeopleSoft finance.
We tracked the number of cycles and the CPU time for the peoplecode event PTS_CFGSRCH_CL.StandardSearch.OnExecute.
Used the below trace option for checking performance issues,
TracePC = 448
TraceSQL=255
Test result
The Components checked are, Expense sheet, PO Inquiry, Travel Auth inquiry and BI Entry pages .  The above list of content references/components where more search executed often by our users are obtained from below SQL
select PTS_SEARCH_ID, COUNT(*) from PS_PTS_RCTSRC_DEF  GROUP BY PTS_SEARCH_ID ORDER BY 2 DESC; 
Search Parameter is default search with minimal required attributes on the delivered pages. We observed that CPU time and number of cycles were less when the default search setup is 100.  So I am thinking this might be the reason Oracle delivered default search results to display the first 100 rows.
So we decided to revert back our Global default search result to 100 and used configurable search configuration per  components to show 300 rows in search  on a case by case basis. 
0 comments
40 views

Permalink