up on the first reqeust to the application? Make sure that you're locking
them correctly, effectively single threading requests until the first
request has finished initializing everything. That's has the side effect of
piling up all kinds of requests on the server that are just waiting for the
initialization to commence, and then when the first request finishes,
they'll all be released to do their tasks.
You could use a short timeout on the CFLOCK tag that prevents multiple
requests from initializing the app vars, catch the exception, and abort the
request at that point. That'd make sure that no requests were stacking up,
but at the expense of not servicing requests until the app is up and
running.
Also, you might consider switching the "save class files" setting in the CF
admin. If you've got a huge number of files, it's probably faster to leave
it unchecked (scanning huge directories is expensive), but if you have a
smaller number, it'll be faster with it checked, because CF won't have to
recompile everything when it starts.
Cheers,
barneyb
> -----Original Message-----
> From: Brook Davies [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 29, 2004 12:41 PM
> To: CF-Talk
> Subject: Debugging CFMX
>
> My CFMX server has tons of trouble starting up under load. Is there a
> debugging method I can use to see exactly what each thread is
> doing when
> trying to start up or someother way I can find the problem?
>
> Brook
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
