That is true, but if you have any functions/apps, that may take longer to return results, and designed to do that, it can sku the AvgQryProcTime.

You probably have certain core functions/apps, that are used heavily. Use timers to check their performance during peak traffic times also. When I am writing new apps and optimizing or debuggin, I will make timers that just test the time a certain db action took, or a certain processing loop took. Then hide the timers in comments in your response HTML.

You can hit these pages yourself during peak times and view the timers. You will get a feel for what is going on. Also, you can set up something, on an external system, that hits a function, and reads the timers out of the results and logs them.

Lastly, and these are just suggestions, but I am an extremely visual person. I setup performance monitors, and watch them after introducing new code, or hardware, or very busy periods. I can see the cpu time of each witango process, and other counters. Anyway, it helps me get a quick handle on things.



-- 

Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
On Nov 8, 2005, at 12:18 PM, Robert Shubert wrote:

I am speaking of Witango requests there, ie. pageviews. In other words, if you have 4 CPU cores, and you strive for a reasonable average request processing time of ½ second, your system should be able to approach 8 requests per second before contention becomes a problem. I recently tested my systems to handle 140 requests/sec (non-db) or about ½ million per hour. I have 8 CPU cores total. I know that most requests make use of the db, sometimes considerably, but the average request processing time over several hours of running should be between 1/3 and ½ of a second on most of today’s servers, providing the code isn’t wasteful.

 

Robert

 


From: Alan Wolfe [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 08, 2005 2:54 PM
To: [email protected]
Subject: Re: Witango-Talk: Server setup question

 

 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


Reply via email to