Cathal, I might have found another issue which I'll crosspost to support. While it does seem that the call to TabController.getTabsByParent(parentId, portalId) is cached so it doesn't hit the database.. once you iterate over the collection it issues a database SP call for each tab resulting in N database calls. This may affect performance all around the site as I see the pattern of code like this:
foreach (TabInfo objTab in GetTabsByParent(ParentId, PortalId)) {
// do something with the tab... causes a query for each tab at a time
}

Is there a way to indicate that we intend to use the whole collection so select all of the tabs in 1 query? Should this be the default?

I searched through the DNN source and modules source and you are correct. This pattern only shows up when deleting all child tabs of a page.  Unfortunately I was using GetTabsByParent in a custom module I'm writing to pull links to content from other parts of the site.  I've already written my own stored procedure to do what I need in a quicker way at the expense of that proc being tied to the schema.  So in a future update my procedure could break instead of relying on the API which has a formal deprecation timeline.

tl;dr No performance problem in daily use. Bummer I can't just use the API with eager fetching.

Same here. I think we should wait for 6.2.1 or something.

But personally i believe that all this social fuzz will put a lot of load to DNN and it will not be suitable for shared hosting plans (even premium ones like mine). It will need a high performance dedicated server, making DNN of no use for a large established community that uses CE 5x or 6.1.

 

---

Discover Venice