Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Hi Axi,
I do know that EPi (on the CMS side) often has issues with its page tree or media tree is there are "too many" pages/assets within a node. Sometimes this slowness is caused by too many pages/assets in the root node.
In the Catalog UI context, something similar is probably happening. If you have a few hundred entries within a node, you could try moving those entries into other nodes (thus reducing the number of entries in a given node) and see if that'll increase performance.
Hi,
That's very strange. In our test environment, a single average VM can handle a node with more than 2000 entries with easy. So I would suggest you to profile your site to see what is the bottleneck.
Regards.
/Q
Hi Quan,
thanks for your input. I'll try to see what's causing the slow performance on the Catalog UI.
Do you have any sugestions how to do that ? are there any tools that you would reccomand me to use..?
Regards,
Axi :)
I trust dotTrace, and SqlProfiler can give some insightful information.
Regards.
/Q
Hi,
Check if its taking time in loading Images on catalog UI?
Threshold for using the simplified mode can be configured using the SimplifiedCatalogListingThreshold appSetting
appSettings> <add key="SimplifiedCatalogListingThreshold" value="1000" /> </appSettings>
change value to 1or 5 an dtest is it still slow.
Regards
Khurram
Hi,