Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Performance Issues w/o Caching

  Asked By: Karissa    Date: Jun 07    Category: Sharepoint    Views: 876

We have a site that we're building out and we're seeing page load
times of around 8 seconds to load. Now this is only happening on the
first page load -- we have output caching enabled and subsequent loads
are near instant.

Does anybody else experience this kind of significant delay on first
page loads? Is there anything we can do to make it load quicker? Or
prepopulate the cache so that users during this phase can have a
better experience?



9 Answers Found

Answer #1    Answered By: Joe Hart     Answered On: Jun 07

Take a look at blog:

Answer #2    Answered By: Jorge Cole     Answered On: Jun 07

Yes, it could just be JIT compiling.

Answer #3    Answered By: Rodolfo Tate     Answered On: Jun 07

Hope you don't mind a newbie jumping in here but I have a relative

What is it that makes loading the home page  so slow? I mean what is the
cause? I have two SPS 3 sites in test environments and they both are
painfully slow. I have just the SPS 3 using SQL Express on fairly good
boxes. No users  touch the sites except me.

I searched the archives and couldn't find anything so I'm asking here.

Answer #4    Answered By: Jesus Foster     Answered On: Jun 07

What type of page  is it? Publishing?

How many Web parts? What are the Web parts? Using audiences? Custom
navigation? Audientized navigation? Are you using BLOB caching? How many
app pools? What type of Hardware? Load balanced?

It could be one of 23,458 problems, but we can try to help you out!

Answer #5    Answered By: Alfredo May     Answered On: Jun 07

My gut is thinking too that it could be the JIT compiling, but an 8
second first page  load seems a bit excessive.

All of the pages are publishing pages, each with many (some up to
10-12) user controls on the page. We're not currently using
audiences. We do have custom navigation which displays all of the
children and crawls back up to the root node of the site  to display
the path.

We are taking advantage of site collection output  and object caching,
don't have BLOB caching  enabled because we're not storing many big
objects in the CMS, maybe one or two images on a page (both <25 KB).

We have 2 app pools, one for our main site and one for the SSP. It's
a two server setup (one web app/one sql server db), with recently
bought hardy machines.

We actually use Joel's warmup scripts
(blogs.msdn.com/.../697044.aspx) after we
do iisresets. But I didn't think that would have an effect on any
pages after the initial first request to the site. Will do some more
testing with that though.

Answer #6    Answered By: Preston Moreno     Answered On: Jun 07

Does anybody have any numbers on how long their applications are
taking to JIT compile when a page  is first hit?

Answer #7    Answered By: Rickey Strickland     Answered On: Jun 07

For me, if i don't run the warm up scripts, anything up to about 20 seconds

I've also just built a lab and on there, restarting the app pool, with an OOTB
front page, it takes 8 seconds

Answer #8    Answered By: Jonathan Thompson     Answered On: Jun 07

Excuse my ignorance but what does JIT mean?

Answer #9    Answered By: Taylor Mills     Answered On: Jun 07

Just In Time: .NET DLLs are typically compiled specifically for the
platform that they are running on when they are called. While it is
possible to pre-compile it is uncommon. Hence, we talk about JIT
compiling or JITing assemblies.

It takes some time to do this so the first call always takes longer than
subsequent calls. In not used for a while (I think it is 20 minutes by
default) the assemblies will be dropped from memory requiring they get
recompiled the next time they are invoked.

Didn't find what you were looking for? Find more on Performance Issues w/o Caching Or get search suggestion and latest updates.