Asset Publisher and queries count

In this post, I will mainly describe my expierience with Asset Publisher in Liferay 6.1 (87489 revision). In the previous post I showed how Asset Publisher constructs entry query and how many records it picks up.

The starting point of my test was the following configuration:

• About 10 000 AssetEntries
• First page with 1 Asset Publisher without any filters. It gets ~4900 records.
• Second page with 1 Asset Publisher with categories filter. It gets ~ 300 records.

Following table shows results of my tests.

Scenario	Guest	Logged In user
1st request. Asset Publisher with ~4900 results. 20 per page.	~ 9800 queries to database	~ 29300 queries to database
2nd request. Asset Publisher with ~4900 results. 20 per page.	0 queries to database	~ 29300 queries to database
1st request. Asset Publisher with ~300 results. 20 per page.	~ 900 queries to database	~ 900 queries to database
2nd request. Asset Publisher with ~300 results. 20 per page.	0 queries to database	~ 30 queries to database

Interesting situation is the second row of this table (Asset Publisher with ~4900 results. 20 per page and logged in user). Asset Publisher retrievs 5000 records from database. Now in a loop it sends one query to transform AssetEntry to specific entity (JournalArticle in my case) and sends two queries to check permissions. It gives three queries in one record.

So Liferay sends 2 * (5000 * 3 queries per item) = 30 000 queries. In the trunk version the second query is cached so it gives 15 000 queries.

Fortunately, most of the queries is partially cached.

From a business point of view I want to display 20 articles in one AssetPublisher with pagination so I don’t understand why my portal sends over 30 000 queries to database. It’s a horrible situation when simple task frequently overuses my server resources.

Advertisement