Using FastTrack, I'm trying to render a list of collections for use as navigation (there are 9 categories).
I haven't changed the FastTrack setup much, only changed the language to en-GB and created some more categories.
However the helper "CategoryLink(ProductCollection category)" looping through the 8 collections with ExampleUiHelper.Content.GetCategoryPageForCollection(category.CollectionKey) is taking a very long time/130+ SQL queries - The profiler result can be seen here.
I experienced a similar issue with the tax which was resolved:
Hey Matt - that may very well be a poor implementation on my part of the category page. I also noticed some duplicate readers when rendering the page in the profiler but have not had a chance to dig into them yet. It's actually on my list of "possible" performance tweaks for the 2.2.0.
The problem stems from the fact that the intial paged queries for the entity collections that find the keys for the items in the page are not cached. It's not a big change, to get that in there, but something that needs to be well tested to ensure that things are cleaned up correctly when the category is updated.
I'll make sure to remove "possible" tweaks and move it into the doing it category =)
FastTrack - slow performance of ".GetCategoryPageForCollection()"
Using FastTrack, I'm trying to render a list of collections for use as navigation (there are 9 categories).
I haven't changed the FastTrack setup much, only changed the language to en-GB and created some more categories.
However the helper "CategoryLink(ProductCollection category)" looping through the 8 collections with ExampleUiHelper.Content.GetCategoryPageForCollection(category.CollectionKey) is taking a very long time/130+ SQL queries - The profiler result can be seen here.
I experienced a similar issue with the tax which was resolved:
https://our.umbraco.org/projects/collaboration/merchello/merchello/74247-retrieving-products-using-entitycollectionservice-is-very-slow
Any ideas?
Hey Matt - that may very well be a poor implementation on my part of the category page. I also noticed some duplicate readers when rendering the page in the profiler but have not had a chance to dig into them yet. It's actually on my list of "possible" performance tweaks for the 2.2.0.
The problem stems from the fact that the intial paged queries for the entity collections that find the keys for the items in the page are not cached. It's not a big change, to get that in there, but something that needs to be well tested to ensure that things are cleaned up correctly when the category is updated.
I'll make sure to remove "possible" tweaks and move it into the doing it category =)
is working on a reply...