DotNetNuke

Re: DNN 3.x caching tabs made huge performance improvement with my custom skin (using getTabByName)

ikamiksok — Mon, 24 Oct 2005 17:30:23 GMT

There is no DNN setting. I wrote my own code to cache all my tabs. Was not sure how DNN did it when you use solpart of the menu system. Because with my skin I was doing something not normal and making several direct calls on getTabByName() and that was accessing the DB each time instead of from a cached pool of tabs. So I wrote my own getTabByName() function which retrieves all the tabs from my own cached table of tabIDs and tabnames.

Jason

Re: DNN 3.x caching tabs made huge performance improvement with my custom skin (using getTabByName)

Designer72 — Thu, 20 Oct 2005 21:54:45 GMT

Could you tell me where that setting is and what to do for it?

DNN 3.x caching tabs made huge performance improvement with my custom skin (using getTabByName)

ikamiksok — Tue, 27 Sep 2005 02:56:46 GMT

I'm not an expert but thought I would point this out in case it helps some ppl. In my skin I have my own custom image links. So I don't use the solpart menu system. And my skin would make calls on getTabByName() to get the tabid for each of my links and there are 30 of them.

So everytime my page loaded it made these calls. Very slow on DNN 3.0.13 after I started expanding and adding more portals. I then upgraded to DNN 3.1.1 which does fix some major problem here with the tabs but it still was very slow.

So for me to fix it, I now retrieve and cache all tabs for x hours. I never add extra tabs to my site anyways. And my site is lightning fast now.

So if you are using getTabByName() be careful. I just tested on my site tonight with a 'before and after' and verified it made a big difference (I had 250 + tabs)

I also mention this as I do not know how expensive the tab calls are in a normal website using dnn menu system. Perhaps if someone is looking to make performance improvements this is another area they can do it. Just thought I would mention it just in case.....

Jason