All entries for Wednesday 11 July 2007
July 11, 2007
According to Oracle doc
- User calls: Number of user calls such as login, parse, fetch, or execute. This metic probabaly incorporates all the activities we are interested from a Java developer’s perspective. It includes Select/update/delete/insert
- recursive calls: Number of recursive calls generated at both the user and system level. An example of call at user level: a SQL call a store procedure which contains a chunk of SQLs. System recursive call are additional calls for housekeeping such as space management, etc.
- Execute count: total number of calls (user and recursive) that execute SQL statements. Does that includes “select” statement? I assume not.
To varify my undstanding of these concepts I wrote a program doing DML against a test database. Result is here
based on Java 3 tier app using JDBC :
- Execute Count = No. of select/insert/delete/update. For easier understanding. do not think it includes recursive calls as doc indicated.
- Recursive Calls = No. of update/insert/delete + Ceiling(Hard parse)
- User Commit = min(No. of update/insert/delete)
- User Calls = No. of select/insert/delete/update + N * Hard Parse (where N =2 when select and N =1 otherwise.)
- All SQLs in a function will includes in EC, UC.
- A function call will have one RC , one EC and UC
- A sample took from live server : User Calls = 509; Execute Count = 174, Recursive Call = 57 User Commit = 5
- The app does not use function, so Execute Count is the number of DMLs send from hibernate to database.
- User Calls is high, it is from hard parse. So the app should use bind variable.(might not true?)
- Recursive Calls are from hard parse and update/delete/insert. Since user commit is low, so most of RC are hard parse.
Another sample: User Calls = 3872; Exeucte : 1237; Recursive: 28
Recusive is low, so function call and hard parse is low. Why User Calls is so higher than Execute Count??
delete from user_preferences WHERE forumid=550 and userid=30387 and name='mailPriority' and value='0'
apparantly cached hard parse cause User Calls high. Cached hard parse wont incure many recursive calls since they are cached. however, one cached hard parse will always generate one user calls.
Action: Ask our developer to use bind variable for this SQL
Expectation: User calls will dropped to EC value.
Use -Duser.language=en to set the lanaugae enviroment in Java application.