Optimizing Oracle performance /
Oracle system performance inefficiencies often go undetected for months or even years--even under intense scrutiny--because traditional Oracle performance analysis methods and tools are fundamentally flawed. They're unreliable and inefficient. Oracle DBAs and developers are all too familiar wit...
Clasificación: | Libro Electrónico |
---|---|
Autor principal: | |
Otros Autores: | |
Formato: | Electrónico eBook |
Idioma: | Inglés |
Publicado: |
Sebastopol, CA ; Farnham :
O'Reilly,
2003.
|
Edición: | 1st ed. |
Temas: | |
Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Table of Contents; Foreword; Preface; Why I Wrote This Book; Audience for This Book; Structure of This Book; Which Platform and Version?; What This Book Is and Is Not; About the Tools, Examples, and Exercises; Citations; Conventions Used in This Book; Comments and Questions; Acknowledgments; Part I; A Better Way to Optimize; "You're Doing It Wrong"; Requirements of a Good Method; Three Important Advances; User Action Focus; Response Time Focus; Amdahl's Law; All Together Now; Tools for Analyzing Response Time; Sequence Diagram; Resource Profile; MethodR; Who Uses the Method
- The abominable smokestackThe optimal performance analyst; Your role; Overcoming Common Objections; "But my whole system is slow"; "The method only works if the problem is the database"; "The method is unconventional"; Evaluation of Effectiveness; Targeting the Right User Actions; Specification Reliability; The System; Economic Constraints; Making a Good Specification; User Action; Identifying the Right User Actions and Contexts; Prioritizing the User Actions; Determining Who Will Execute Each Action and When; Specification Over-Constraint; Targeting the Right Diagnostic Data
- Expectations About Data CollectionData Scope; Scoping Errors; Long-Running User Actions; "Too Much Data" Is Really Not Enough Data; Oracle Diagnostic Data Sources; For More Information; Targeting the Right ImprovementActivity; A New Standard of Customer Care; How to Find the Economically Optimal Performance Improvement Activity; Making Sense of Your Diagnostic Data; Forecasting Project Net Payoff; Forecasting Project Benefits; Monetizing the benefits; If you can't monetize the benefits; Forecasting Project Cost; Forecasting Project Risk; Part II; Interpreting Extended SQL Trace Data
- Trace File Walk-ThroughExtended SQL Trace Data Reference; Trace File Element Definitions; Cursor numbers; Session identification and timestamps; Application identification; Cursor identification; Database calls; Wait events; Bind variables; Row source operations; Transaction end markers; Reference summary; Oracle Time Units; Response Time Accounting; Time Within a Database Call; Time Between Database Calls; Recursive SQL Double-Counting; Parent-child relationships; Recursive statistics; Evolution of the Response Time Model; Walking the Clock; Oracle Release 8 and Prior; Oracle Release 9
- Clock Walk FormulasForward Attribution; Forward Attribution for Within-Call Events; Forward Attribution for Between-Call Events; Detailed Trace File Walk-Through; Exercises; Collecting Extended SQL Trace Data; Understanding Your Application; Activating Extended SQL Trace; Tracing Your Own Source Code; Tracing Someone Else's Source Code; Triggering a session to activate its own trace; Activating trace from a third-party session; Finding Your Trace File(s); Trace File Names; Simple Client-Server Applications; Oracle Parallel Execution; Oracle Multi-Threaded Server