Salesforce

For Web 8.5, production website load results in database server resource utilization spiking after upgrade

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentWeb 8.5
Symptoms/Context
- Customer has upgraded from Tridion 2013 SP1 HR1 to Web 8.5.
- In lower environments, stress testing did not indicate significant DB server resource utilization spiking.
- In production environment, live website load resulted in immediate database server resource spiking.
- Hotfix CD_8.5.0.17761 has been applied to all microservices in CD environment.
- Spikes only overlap with higher website traffic, not publishing activity.
- Website heavily leverages taxonomy keywords.
- Query which is associated with high DB server load is
(@P0 int,@P1 int,@P2 int)select count(distinct relatedkey2_.ITEM_REFERENCE_ID) as col_0_0_ from TAXFACETS taxonomyit0_ cross join 
TAXFACETS taxonomyit1_ cross join ITEM_CATEGORIES_AND_KEYWORDS relatedkey2_ where taxonomyit0_.NAMESPACE_ID=taxonomyit1_.NAMESPACE_ID and 
taxonomyit0_.PUBLICATION_ID=taxonomyit1_.PUBLICATION_ID and taxonomyit0_.TAXONOMY_ID=taxonomyit1_.TAXONOMY_ID and taxonomyit0_.NAMESPACE_ID=@P0 and 
taxonomyit0_.PUBLICATION_ID=@P1 and taxonomyit0_.FACET_ID=@P2 and taxonomyit1_.TAXONOMY_ID=relatedkey2_.TAXONOMY_ID and 
taxonomyit1_.FACET_ID=relatedkey2_.KEYWORD_ID and relatedkey2_.NAMESPACE_ID=taxonomyit1_.NAMESPACE_ID and 
relatedkey2_.PUBLICATION_ID=taxonomyit1_.PUBLICATION_ID and taxonomyit1_.FACET_LEFT>=taxonomyit0_.FACET_LEFT and 
taxonomyit1_.FACET_RIGHT<=taxonomyit0_.FACET_RIGHT group by taxonomyit0_.NAMESPACE_ID , taxonomyit0_.PUBLICATION_ID , taxonomyit0_.FACET_ID
- Hotfix CD_8.5.0.14124 has been applied, as discussed in KB article SDL Web 8.5 Deployer failing with java.nio.file.NoSuchFileException error due to missing indexes
- In the Deployer and Content Service cd_storage_conf.xml files, CountEnabled attribute is set to false as discussed in KB article For Web 8.5, the publishing / unpublishing process takes too long
Resolution
Production performance issue resolved by administrator after adding database caching.
Root Cause
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by