RE: Computing resource consumption

[Cary Millsap]

Title: RE: Computing resource consumption

You have a good point. I’d expect that most bg workload performed on behalf of a session is probably writes, so measuring redo generation might be an excellent addition. It also encourages users (and hence, indirectly, applications developers) to be economical with their redo generation, which is good too. (One example of an application that generates redo when it doesn’t need to is an UPDATE that changes a column to a value it already had.)   Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com Upcoming events: - Hotsos Clinic 101 in Denver, Sydney - Hotsos Symposium 2004 March 7–10 Dallas - Visit www.hotsos.com for schedule details... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jamadagni, Rajendra Sent: Friday, July 25, 2003 8:30 AM To: Multiple recipients of list ORACLE-L Subject: RE: Computing resource consumption   Thanks Cary, thanks, but here is a question ... you say capturing physical IO is redundant ... what about REDO  generated by session? Isn't that part of physical writes? If I just concentrate on LIO (I am currently using "Logical IO' (statistic#9 in 9202). Currently I am concentrating on following statistics to create a matrix   9 -- session logical reads  12 -- CPU used by this session   20 -- session pga memory  21 -- session pga memory max  42 -- physical reads  46 -- physical writes 115 -- redo size 236 -- bytes sent via SQL*Net to client 237 -- bytes received via SQL*Net from client not sure if all of them will matter in the end, but at-least it is a start for me. Another problem is capturing the work done by background processes on behalf of these sessions ... how does one go about capturing that workload?? Thanks in advance Raj -------------------------------------------------------------------------------- Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art ! -----Original Message----- From: Cary Millsap [mailto:[EMAIL PROTECTED]] Sent: Friday, July 25, 2003 1:24 AM To: Multiple recipients of list ORACLE-L Subject: RE: Computing resource consumption   Raj, A pretty common (and actually pretty accurate) charge back unit is the LIO. You can get this information by using the standard AUDIT CONNECT feature, and using the LREAD value as your basis. If you wanted to get fancy, you might also charge by the parse call (which you're already collecting in your V$SESSTAT query). The reason I'd focus on these two metrics is because these are the two operations on an Oracle system that absolutely prevent the system from scaling. You could count physical I/Os as well, but that would be redundant if you're already catching LIO call counts. Cary Millsap Hotsos Enterprises, Ltd. http://www.hotsos.com Upcoming events: - Hotsos Clinic 101 in Denver, Sydney - Hotsos Symposium 2004 March 7-10 Dallas - Visit www.hotsos.com for schedule details... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jamadagni, Rajendra Sent: Thursday, July 24, 2003 12:04 PM To: Multiple recipients of list ORACLE-L Subject: Computing resource consumption Does anyone know any papers or techniques to compute resource consumption by users in a DB systems? This may or may not be for computing charge-back to the client, but my questions are 1. What do you compute? 2. are there any standard methods and or standard formula? I am collecting v$sesstat when a session exits, but is data alone from session stats sufficient? How about the work done by background processes on user's behalf? Do you do anything like this at your workplace? This is something that might be coming down the line, so I have been asked to start looking for related stuff. Thanks in advance Raj -------------------------------------------------------------------------------- Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email are strictly personal. QOTD: Any clod can have facts, having an opinion is an art !