DNN Community Forums

SearchResults Localization Memory Overhead

Sort:

You are not authorized to post a reply.

Author

Messages

G

New Member

Posts:

12/8/2012 1:00 AM

I noticed every-time I callDotNetNuke.Services.Search.SearchDataStoreProvider.Instance().GetSearchItems(_ModuleInfo.PortalID, _ModuleInfo.TabID, _ModuleInfo.ModuleID)there seems to be many calls to DNN localization provider. Say you have 30K searchResults & all make a call to get translated; those imutable strings add up quickly. I think DNN is converting them ToLower() or something like that. After calling that for every module I ended up with a w3wp.exe "Working Set" of memory 4gb large. A good portion of that space was used by strings.Just FKY, don't really need resolution for this.

samyb

New Member

Posts:

12/10/2012 10:28 AM

Hello Gary,

thank you for reporting this; what happens is that the search results contain two fields that are translated after search, ItemType and ItemGroup. These two fields allow a user to categorize the search items according to what is set in the resource file.
However from what i saw while testing your find, when a search is launched the number of search item should be equal to the paging size. So even if 30k search items are matching your query you should only have a subset of those items who call Localization, unless you don't use paging.

Could you give me some more info regarding the call stack that you're seeing; if it is indeed the lack of paging that causes all these Localization calls, i will try and change the system to lazily call the DNN Localization service in order to minimize the load.

Best regards,
Samy

You are not authorized to post a reply.