HomeHomeUsing DotNetNuk...Using DotNetNuk...Performance and...Performance and...DNN Search very slow after bugfix 14543DNN Search very slow after bugfix 14543
Previous
 
Next
New Post
6/10/2012 8:15 PM
 
Hi,Ik noticed the standard DNN Search on my DNN community version 06.01.03 was very slow, compared to another DNN installation.After much digging I found the difference between the versions lying in the SP "GetSearchResultsByWord".There seems to have been a bugfix:/* Fix bug 14543: Update GetSearchResultsByWord to exclude deleted tab modules*/It modyfies the SP to include the clause "AND (tm.IsDeleted = 0)"When I remove this clause again, the SP runs a 100 times faster!!I understand that the clause needs to be added again, but does anyone know why it is such a performance killer?Thanks in advance!RikBelow I pasted a copy the SP [GetSearchResultsByWord] SELECT si.SearchItemID, sw.Word, siw.Occurrences, siw.Occurrences + 1000 AS Relevance, m.ModuleID, tm.TabID, si.Title, si.Description, si.Author, si.PubDate, si.SearchKey, si.Guid, si.ImageFileId, u.FirstName + ' ' + u.LastName As AuthorName, m.PortalId FROM dbo.SearchWord sw INNER JOIN dbo.SearchItemWord siw ON sw.SearchWordsID = siw.SearchWordsID INNER JOIN dbo.SearchItem si ON siw.SearchItemID = si.SearchItemID INNER JOIN dbo.Modules m ON si.ModuleId = m.ModuleID LEFT OUTER JOIN dbo.TabModules tm ON si.ModuleId = tm.ModuleID LEFT JOIN dbo.TabModuleSettings tms ON tms.TabModuleID = tm.TabModuleID AND tms.SettingName = 'DisableSearch' INNER JOIN dbo.Tabs t ON tm.TabID = t.TabID LEFT OUTER JOIN dbo.Users u ON si.Author = u.UserID WHERE (((m.StartDate Is Null) OR (GetDate() > m.StartDate)) AND ((m.EndDate Is Null) OR (GetDate() < m.EndDate))) AND (((t.StartDate Is Null) OR (GetDate() > t.StartDate)) AND ((t.EndDate Is Null) OR (GetDate() < t.EndDate))) AND (sw.Word = @Word) AND (t.IsDeleted = 0) AND (m.IsDeleted = 0) AND (tm.IsDeleted = 0) -- This is the performance killer!! AND (t.PortalID = @PortalID) AND (tms.TabModuleID is NULL) ORDER BY Relevance DESC
 
New Post
6/11/2012 7:53 AM
 
please log it as a bug to support.dotnetnuke.com - the logic appears correct but we may need to rewrite the query to use more efficent sql or else add some indexes to improve performance.
 
Previous
 
Next
HomeHomeUsing DotNetNuk...Using DotNetNuk...Performance and...Performance and...DNN Search very slow after bugfix 14543DNN Search very slow after bugfix 14543


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:

1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Attend A Webinar
Start  Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke (DNN) provides a suite of solutions that make designing, building and managing feature-rich sites and communities fast, easy and cost-effective. The DotNetNuke Platform CMS is the foundation for more than one million websites worldwide. DNN Social, our newest solution, enables businesses to create immersive, interactive communities. Thousands of organizations like True Value Hardware, Bose, Cornell University, Glacier Water, Dannon, Delphi, USAA, NASCAR, Northern Health and the City of Denver have leveraged DNN to deploy highly engaging business- critical websites. Our rapid growth in product sales and deployments resulted in DotNetNuke Corp. being named one of the fastest growing private companies in America by Inc. Magazine in 2011 and 2012.