With Workplace Web Content Management (WWCM) 6.0.1.3 API , the performance had been not as expected. To give a scenario, following are the implementation steps for retrieving a piece of information:
- Retrieve user’s workspace
- Get Authoring Template Id
- Retrieve Site Area Id
- Content Search based on Authoring Template, Site Area
- GetIds of all the content list retrieved from Content Search
- Retrieve Content based on specific requirement from the Content Search result
- Return back the content item
The average amount of time taken is between 0.4 to 0.6 seconds. Out of which % of time taken for retrieving Document Ids for Authoring Template and Site Area forms 50 % of the time to retrieve information. So, if a portlet/page has 6 calls for content, the total time for just WCM is between 2.4 to 3.6 seconds which doesn’t meet SLAs for a page load. This basically lead to defining WWCM Site Structure caching design pattern.