I applied all modified files in issue LPS-13979 but asset publisher is slow too
I am having the same issue. We had to disable the Asset Publisher on our Wiki site because it slowed everything down to a crawl.
How can I assist in fixing this issue ASAP?
I have the same problem.
On my production portal there is 30 000 articles and I have 20 users. If all users send requests some pages render very slow. IMHO there is a big query, which get count to asset publisher portlet (dynamic mode). AssetEntryFinderImpl and countEntries method kills my portal.
Time of execute this query is about 20s. What can I do with it?
I make some changes in AssetEntryFinderImpl.
I remove 'DISTINCT' keyword and remove ORDER BY title. now my performance is better but not qualified
I've changed the issue type to improvement and changed the priority to major.
For those that have tried applying some of the suggested improvements, it would be appreciated if you could contribute a patch and specify the tests that have been done to ensure that all the Asset Publisher features are still working as expected.
Fix is to create a few indexes.
create index IX_75D42FF9 on AssetEntry (expirationDate);
create index IX_2E4E3885 on AssetEntry (publishDate);
create index IX_9029E15A on AssetEntry (visible);
This is being bulk closed in preparation for the new workflow.
Why AssetEntry finder queries not use hql?
I think AssetEntry finder queries not cached with ehcache. is it correct? is there any way to make sure this query hits level-2 cache?