Yeah, fortunately most of the time is spent waiting for the http responses
which uses no system resources so the templates just run in the background
and don't even make a noticeable mark on the CPU usage.

> -----Original Message-----
> From: Robertson-Ravo, Neil (RX)
> [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2004 12:14
> To: CF-Talk
> Subject: RE: Disabling request timeouts
>
> Jeez..hefty!
>
>  
>
>    _____  
>
> From: James Smith [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2004 12:07
> To: CF-Talk
> Subject: RE: Disabling request timeouts
>
>  
>
> The time is actually caused by looking up a couple of
> thousand web pages (by
> cfhttp) and processing the returned pages to extract some info.
>
> > -----Original Message-----
> > From: Robertson-Ravo, Neil (RX)
> > [mailto:[EMAIL PROTECTED]
> > Sent: 23 September 2004 12:00
> > To: CF-Talk
> > Subject: RE: Disabling request timeouts
> >
> > Though really if you are running a page for 30 mins then I
> would look
> > at an alternative approach...I would assume that the length
> of time to
> > run it due to SQL...maybe look at DTS.
> >
> >  
> >
> >    _____
> >
> > From: James Smith [mailto:[EMAIL PROTECTED]
> > Sent: 23 September 2004 11:55
> > To: CF-Talk
> > Subject: Disabling request timeouts
> >
> >  
> >
> > I want to have a global request timeout on the server of about 30
> > seconds but there are a few (3 so far) templates that I need to be
> > able to run for up to 30 minutes.  Is there no way to disable the
> > timeout for an individual template or am I going to have to
> disable it
> > in the administrator and then enable it one page at a time with the
> > cfsetting tag?
> >
> > --
> > James Smith
> > [EMAIL PROTECTED]
> >
> >    _____
> >
> >
> >
> >
>
>    _____  
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to