Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
Environment:Tomcat 5 + MySQL 5.5. Portal 6.2.x GIT ID: f6e0b3a667723dfb08e66b13db650170623c71df
1 - Turn on hibernate.show_sql=true in portal-ext.properties.
2 - Monitor SQL statements issued by the portal.
3 - In Liferay, add an Asset Publisher and 10 Web Contents with the "Liferay Rules" title
4 - Add a Search Portlet and search for the word "Rules"
5 - In Liferay's log search for the following (or very similar) query.
If you have 10 WCs, this will be called 10 times:
Let's denote ...
K: Number of items returned by the search portlet.
N: Number of asset publishers in the portal.
The query above will be executed K times, returning each time N + 1 rows; which means that K(N + 1) rows are fetched from the DB for every search request.
As the Customer reports that their scenario includes ~890 asset publishers per site, database transactions may be hit pretty hard.
Please refer to the following forum thread: https://in.liferay.com/web/global.engineering/forums/-/message_boards/message/1284919