|
Home > Archive > Microsoft Content Management Server > February 2005 > About 1700 queries to the MCMS database on loading a Channel Rende
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
About 1700 queries to the MCMS database on loading a Channel Rende
|
|
| bep@10.10.10.10 2005-02-25, 2:50 am |
| Hello
I have a very slow page which I am trying to speed up. It turns out that the
speed hit is probably to do with the fact that the code on the MCMS web
server exicutes somewhere around 1700 queries to the MCMS databases server.
A SQL Server Profiler trace limiting the trace output to only the MCMS
userid, and only the MCMS database results in about 3500 lines of trace
output.
A whole heap of this sort of stuff:
exec sp_executesql N'SELECT TOP 1 * FROM Node WHERE NodeGUID = @P1 ORDER BY
IsCheckedOutVersion ASC', N'@P1 char(38)', '{InsertUniqueGuidHere}'
Any ideas why this would happen?
Thanks for any help
| |
| bep@10.10.10.10 2005-02-25, 2:50 am |
| Just a followup to my own post.
I put a breakpoint in global.asax on Application_BeginRequest. The 1700 odd
queries are performed after this Application_BeginRequest, but I cannot tell
where. It is before the page_Load of the requested page though.
Thanks for any help.
"bep@10.10.10.10" wrote:
> Hello
>
> I have a very slow page which I am trying to speed up. It turns out that the
> speed hit is probably to do with the fact that the code on the MCMS web
> server exicutes somewhere around 1700 queries to the MCMS databases server.
>
> A SQL Server Profiler trace limiting the trace output to only the MCMS
> userid, and only the MCMS database results in about 3500 lines of trace
> output.
>
> A whole heap of this sort of stuff:
>
> exec sp_executesql N'SELECT TOP 1 * FROM Node WHERE NodeGUID = @P1 ORDER BY
> IsCheckedOutVersion ASC', N'@P1 char(38)', '{InsertUniqueGuidHere}'
>
> Any ideas why this would happen?
>
> Thanks for any help
| |
| Stefan [MSFT] 2005-02-25, 5:49 pm |
| Hi,
this can happen after a server restart when the node cache is empty.
You need to ensure that the node cache is big enought for your site:
http://support.microsoft.com/default.aspx?id=318976
After the node cache has been filled these requests will be resolved from
the cache and do not have to go to the database.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights
Book: Building Websites Using MCMS: http://tinyurl.com/56jt8
----------------------
<bep@10.10.10.10> wrote in message
news:60F6A3B2-64D3-43D0-B985-F8A40E9EADF3@microsoft.com...
> Hello
>
> I have a very slow page which I am trying to speed up. It turns out that
the
> speed hit is probably to do with the fact that the code on the MCMS web
> server exicutes somewhere around 1700 queries to the MCMS databases
server.
>
> A SQL Server Profiler trace limiting the trace output to only the MCMS
> userid, and only the MCMS database results in about 3500 lines of trace
> output.
>
> A whole heap of this sort of stuff:
>
> exec sp_executesql N'SELECT TOP 1 * FROM Node WHERE NodeGUID = @P1 ORDER
BY
> IsCheckedOutVersion ASC', N'@P1 char(38)', '{InsertUniqueGuidHere}'
>
> Any ideas why this would happen?
>
> Thanks for any help
|
|
|
|
|