Method R Discussion Group

Method R helps developers, DBAs, and decision-makers optimize Oracle-based software in every phase of the software life cycle.

Discuss Method R products, techniques, and events.

Ask new questions or post your own responses.

Diagnosing SQL*Net Message Performance - Webinar 6/21/07

If SQL*NET Message from client is the top subroutine in the profile, how do you diagnose that component outside of the database? This could be scattered on the other 2 tiers!
Becky Goodman Send private email
Thursday, June 21, 2007
People are usually surprised by how often you DON'T need instrumentation from other tiers to solve problems that manifest in our profiles as "SQL*Net message from client". (I'll call it "SNmfc" from here on out to save typing.)

In cases where there are many short-duration SNmfc calls, it's usually an indication of a badly designed/coded application that's parsing inside of a loop or failing to use Oracle's array processing features.

However, sometimes the SNmfc time comes from a small number of long-duration calls, where "long" is defined as more time than a network round-trip plus a miniscule bit of code path on another tier should consume. In this case, the prescription is indeed for you to instrument the tiers outside of Oracle where the time is being consumed.

Different architectures require different instrumentation techniques. In the session, I mentioned that one source of information about instrumentation about Apache (for example) is Another article you should consider spending some time with is
Cary Millsap Send private email
Thursday, June 21, 2007

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Discussion Groups Main Page

Powered by FogBugz