Thanks for the reply Stefan

The server has not just been restarted. This behaviour is also consistent. I
can perform the request several times within seconds, and each time it goes
to the database.

Also, why is it getting this much data anyway? This is just displaying a
channel rendering. There is acutally nearly 2000 postings in the channel. Th
e
channel points to a channel rentering ASPX page. Would MCMS need to read
every posting before it figured out it was a channel rendering, and just
forward to the aspx page? Bear in mind that this is just the initial load of
the channel rendering, and I am not reading or displaing any of the postings
within the channel.

Also, I have noted that this behaviour is not happening in our dev
environment. Then I decided to export the data from the prod site into the
dev MCMS database, using the MCMS tools. Still no bad behaviour in dev. It
loads the page lightning fast, and does not make thoudands of round trips to
the SQL Server server.

Then I decided to back up the MCMS database from prod using SQL Server, and
recover it to dev. After some tweaking with permissions, it now does exibit
the bad bevaviour discovered in prod. The page takes a long time to load (10
to 12 sec, as opposed to about a second for other pages), and makes abour
1500 to 2000 round trips to SQL server.

Any further help appreciated.

Thanks
David

"Stefan [MSFT]" wrote:

> 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... 
> the 
> server. 
> BY 
>
>
>

[ Post a follow-up to this message ]