Joe's comments are a very valid see #2 below. As we all know, all of our
applications run just fine until you get them out of the lab and put them
under load or add a lot of data.
Some other basics:
1. turn on the debug in CF Admin. and see how long it is taking to process
some of your queries. You might be surprised to find one or two that are
killing your application or running more times than needed. Maybe they are
taking an extra long time to process for a variety of reasons. Possible
solutions, they could be re-written, index fields as necessary or maybe use
a stored procedure. ( I had this exact issue happen on an app that I
licensed, it killed the server under load, worked beautifully when testing
& when we fixed the problem it ran/runs great ).
2. make sure that what you are running in your applicaton.cfm does not get
reloaded every time especially if it is a query (another database hit) and
you don't need it to do so.
3. Look up fine tuning tips for various settings in your CF Admin such as
sizes of templates, cache, simultanous users at the macromedia website.
4. Check available RAM and other server resources. Put your SQL db on
another box and if you cannot, make sure you restrict how much maximum RAM
SQL is allowed to use.
Bob Coalter
InterNet Partners, Inc.
www.internet-partners.com
At 01:23 PM 8/16/2005 -0500, you wrote:
If I was designing the site, I'd move all variables that had to be
unique to each site into session variables. This way I wouldn't have
to worry about my application variables getting mixed up between
sites, especially with all the server wide includes that probably
depend on and make calls to the application scope. Which is what I
suspect is happening. Each user's session would then retain the
information about the specific site they are on.
HTH,
Joe Kelly
On 8/16/05, Kevin Fricke <[EMAIL PROTECTED]> wrote:
>
> OK, let me tell you a bit more about what we are doing. I am sure that the
> design of the application is the cause...I just don't know where to start.
>
> We have a site that processes online reservations.
>
> We also have hundreds of "clone" sites which we market to get the
bookings.
> Each clone is its own site. Therefore, we have each one set up with it's
> own application name and several application variables. Then each page
> deeper in the site pulls several pages from includes. Each include is
> pulling data from the database. This way if we change a page we only have
> to change it in one place.
>
> Make sense?
>
> Should we be using something other than application variables. As far
as I
> know we are not caching any queries.
>
> Thoughts?
>
> Kevin
--
Thanks,
Joe Kelly
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.10/73 - Release Date: 8/15/2005
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.10/73 - Release Date: 8/15/2005
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
