Todd:
It all really depends. You can't accurately determine the number of users
until your server will crash. It all depends on what the page is doing and
such. However, 3.6 seconds is a lengthy time for a page to be processing.
-Greg
- Original Message -
From: "Todd Ashworth" [EMAIL
Ashworth
- Original Message -
From: "Greg Wolfinger" [EMAIL PROTECTED]
To: "CF-Talk" [EMAIL PROTECTED]
Sent: Friday, December 15, 2000 10:21 AM
Subject: Re: how many milliseconds is too many?
| Todd:
|
| It all really depends. You can't accurately determine the num
ot; [EMAIL PROTECTED]
Sent: Friday, December 15, 2000 10:53 AM
Subject: Re: how many milliseconds is too many?
| However, 3.6 seconds is a lengthy time for a page to be processing.
Yes, it is. That's why I was concerned about how much of an impact it
would
have on the application and the serve
: Todd Ashworth [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Date: Friday, December 15, 2000 11:06 AM
Subject: Re: how many milliseconds is too many?
| However, 3.6 seconds is a lengthy time for a page to be processing.
Yes, it is. That's why I was concerned about how much of an impact
Want to post your code for some Friday Afternoon fun
Justin MacCarthy
The page pulls data from 6 different tables and performs several loops in
the process. Unfortunately, I can't figure out how to make it go any
faster. I'm sure a stored procedure would help, but it was all I could do
uot;CF-Talk" [EMAIL PROTECTED]
Sent: Friday, December 15, 2000 10:21 AM
Subject: Re: how many milliseconds is too many?
| Todd:
|
| It all really depends. You can't accurately determine the number of users
| until your server will crash. It all depends on what the page is doing
and
| such.
This may not apply to your situation, but it is worth investigating.
Consider creating a shadow database (possibly denormalized) to
address the performance issue...
organize the data to fit the specific processing requirements of
your most frequently used queries. Then take
15, 2000 12:08 PM
To: CF-Talk
Subject: RE: how many milliseconds is too many?
This may not apply to your situation, but it is worth investigating.
Consider creating a shadow database (possibly denormalized) to
address the performance issue...
organize the data to fit the specific
I am reminded of a quote from my years at IBM:
"A job worth doing, is worth doing poorly... if there is no other choice"
I could be wrong, but I believe the quote "A job worth doing, is worth doing
poorly" originated in John Gall's book "Systemantics". The original edition
from the 70's is
Actually, Sybase, but views are a great idea. Thanks all!
Todd
- Original Message -
From: "Rick Lamb" [EMAIL PROTECTED]
To: "CF-Talk" [EMAIL PROTECTED]
Sent: Friday, December 15, 2000 2:03 PM
Subject: RE: how many milliseconds is too many?
If your using MS SQL,
Say I have a page that takes about 3,600 ms to process. Does
anyone know how much traffic that page can handle before
killing the server .. or at least until the app becomes
unusable?
There are lots of other variables you'd have to provide to answer this
question. How often is the page
11 matches
Mail list logo
