Re: slow to load

From: AVance (avance[atnospamforyou]iowaheart.com)
Date: 07/22/04 

Date: Thu, 22 Jul 2004 08:34:41 -0500

Mike,
The issue is ASP.NET on the web server dynamically reloading the web app.

It depends on how your IIS6 application pool is configured.

One thing to be aware of is that ASP.NET does not technically load the
entire application into the worker process on first request. I have seen
many posts simply state, "ASP.NET worker process is restarting." -- True,
however, ASP.NET also only loads a portion of a DLL (or something like that)
with each request for EACH SUBFOLDER IN YOUR WEB APP. Thus, a request to /
will cause a "slow load" as will /mysite, because now mysite has to load.
Once all the code is loaded, it should be ok.

On your Recycling tab (on the app pool properties), I actually have mine
setup to never recycle. We've had no problems with it. On the performance
tab, check Idle Timeout. This is probably your "1 hour slow load" issue you
describe. You probably have 1 or N worker processes setup, and all the
threads end up being shutdown after a period of time, and when you make a
fresh request, it has to kick those guys into gear. I have mine disabled so
my threads never shutdown. And my Max worker processes are set to 5.

On Health, I enable pinging every 5 seconds, and Enable rapid-fail
protection 5 and 10 respectively. Startup and shutdown time limits are 90
seconds.

I didn't necessarily configure all of those with any scientific fact, those
are actually probably the defaults. We've been having a great success on
sharepoint. One thing I noticed on our PIII dual 900Mhz w/ 512 MB of RAM is
how slow sharepoint seemed to be on load. Once I messed with the app pool
settings, it was a lot better.

"Mike Johnson" <mike_w_johnson@hotmail.com> wrote in message
news:02c001c46feb$a1516400$3a01280a@phx.gbl...
> Hello,
>
> I'm experiencing the same type of issue. I will first try
> to explain my environment so as to head off the obvious
> questions.
>
> All the servers and workstations below are on a private,
> 100M LAN. There is no Proxy or ISA server involved.
>
> I have a web server running Server 2003/IIS6.0. It's a
> PIII 600M with 256M of memory. WSS is running on this
> machine. WSS is configured to communicate to my SQL
> server via IP address. The hard disks never spin down.
>
> I have a SQL server running Server 2003 and SQL 2000 with
> SP3 loaded. It's a PIV 1.3G with 700M of memory. Named
> Pipes is disabled and all communication to SQL uses TCP/IP
> and Port 1433. An alias is also established to use the IP
> address and port 1433. The hard disks never spin down.
>
> Using a seperate Win2K workstation, I access the WSS site
> via IP address. The first time I access the site, it
> takes at least 20 seconds for the WSS site to come up. It
> almost acts like the SQL database is asleep and then wakes
> up.
>
> I can then clear my cache and all Temporary Internet files
> on my Win2K workstation and hit the WSS site again. It
> will pull up the site in approximately seven seconds.
> However, if I wait for some period of time and then hit
> the WSS site again, it will once again take 20 seconds for
> the site to come up. I usually wait at least an hour, but
> I'm not sure what the cutoff period is. Once again, it
> acts like the database is asleep and must wake up.
>
> The problem is not workstation related because I've tried
> on multiple machines. The same problem is experienced
> when accessing my WSS site via the Internet, but
> exacerbated due to Internet delay.
>
> I know it's not best practice, but I tried running IIS and
> SQL on the same PIV 1.3G, 700M of memory machine in an
> attempt to eliminate the problem, but I was unsuccessful.
>
> Any suggestions at all would be greatly appreciated.
>
> Thanks,
> Mike Johnson
>
>
>
> >-----Original Message-----
> >It's always slow to load the first page in a browser
> session because it has
> >to load a mass of files that the browser may later need
> to render pages. If
> >my memory is right that mass of files is in total
> something like 2MB.
> >
> >As other correspondents have noted, it's more noticeable
> over slow links but
> >it's still caused by the same files.
> >
> >You'll find that Mozilla firefox 0,9 is faster but you
> miss an awful lot of
> >functionality (Data*** View; Multiplle Document Uploads
> etc.)
> >
> >Mike Walsh, Helsinki, Finland
> >WSS FAQ at wss.collutions.com
> >Please reply to the newsgroup
> >
> >"Ashton" <colin.ashton@nww-tr.wales.nhs.uk> wrote in
> message
> >news:uBZgTcnaEHA.2260@TK2MSFTNGP10.phx.gbl...
> >> Is the sharepoint site slow to load generally?
> >> "Define slow"
> >> On the server can take 5 secs for the initial page of
> the site, then image
> >> are a second later. (images stored on other virtual
> servers) same
> >physical
> >> server.
> >> Without going into details of specs, its just generally
> slower then other
> >> non teams sites on the same IIS server.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >.
> >

Loading