• Complain

Murali Vallath - Expert Oracle RAC Performance Diagnostics and Tuning

Here you can read online Murali Vallath - Expert Oracle RAC Performance Diagnostics and Tuning full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley, CA, year: 2014, publisher: Apress, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Murali Vallath Expert Oracle RAC Performance Diagnostics and Tuning
  • Book:
    Expert Oracle RAC Performance Diagnostics and Tuning
  • Author:
  • Publisher:
    Apress
  • Genre:
  • Year:
    2014
  • City:
    Berkeley, CA
  • Rating:
    5 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 100
    • 1
    • 2
    • 3
    • 4
    • 5

Expert Oracle RAC Performance Diagnostics and Tuning: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Expert Oracle RAC Performance Diagnostics and Tuning" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Expert Oracle RAC Performance Diagnostics and Tuning provides comprehensive coverage of the features, technology and principles for testing and tuning RAC databases. The book takes a deep look at optimizing RAC databases by following a methodical approach based on scientific analysis rather than using a speculative approach, twisting and turning knobs and gambling on the system.

The book starts with the basic concepts of tuning methodology, capacity planning, and architecture. Author Murali Vallath then dissects the various tiers of the testing implementation, including the operating system, the network, the application, the storage, the instance, the database, and the grid infrastructure. He also introduces tools for performance optimization and thoroughly covers each aspect of the tuning process, using many real-world examples, analyses, and solutions from the field that provide you with a solid, practical, and replicable approach to tuning a RAC environment. The book concludes with troubleshooting guidance and quick reference of all the scripts used in the book.

Expert Oracle RAC Performance Diagnostics and Tuning covers scenarios and details never discussed before in any other performance tuning books. If you have a RAC database, this book is a requirement. Get your copy today.

  • Takes you through optimizing the various tiers of the RAC environment.
  • Provides real life case studies, analysis and solutions from the field.
  • Maps a methodical approach to testing, tuning and diagnosing the cluster

Murali Vallath: author's other books


Who wrote Expert Oracle RAC Performance Diagnostics and Tuning? Find out the surname, the name of the author of the book and a list of all author's works by series.

Expert Oracle RAC Performance Diagnostics and Tuning — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Expert Oracle RAC Performance Diagnostics and Tuning" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Murali Vallath 2014
Murali Vallath Expert Oracle RAC Performance Diagnostics and Tuning 10.1007/978-1-4302-6710-2_1
1. Methodology
Murali Vallath 1
(1)
NC, United States
Performance tuning is a wide subject, probably a misunderstood subject; so it has become a common practice among technologists and application vendors to regard performance as an issue that can be safely left for a tuning exercise performed at the end of a project or system implementation. This poses several challenges, such as delayed project deployment, performance issues unnoticed and compromised because of delayed delivery of applications for performance optimization, or even the entire phase of performance optimization omitted due to delays in the various stages of the development cycle. Most important, placing performance optimization at the end of a project life cycle basically reduces opportunities for identifying bad design and poor algorithms in implementation. Seldom do they realize that this could lead to potentially rewriting certain areas of the code that are poorly designed and lead to poor performance.
Irrespective of a new product development effort or an existing product being enhanced to add additional functionality, performance optimization should be considered from the very beginning of a project and should be part of the requirements definition and integrated into each stage of the development life cycle. As modules of code are developed, each unit should be iteratively tested for functionality and performance. Such considerations would make the development life cycle smooth, and performance optimization could follow standards that help consistency of application code and result in improved integration, providing efficiency and performance.
There are several approaches to tuning a system. Tuning could be approached artistically like a violinist who tightens the strings to get the required note, where every note is carefully tuned with the electronic tuner to ensure that every stroke matches. Similarly, the performance engineer or database administrator (DBA) could take a more scientific or methodical approach to tuning. A methodical approach based on empirical data and evidence is a most suitable method of problem solving, like a forensic method that a crime investigation officer would use. Analysis should be backed by evidence in the form of statistics collected at various levels and areas of the system:
  • From functional units of the application that are performing slowly
  • During various times (business prime time) of the day when there is a significant user workload
  • From heavily used functional areas of the application, and so forth
The data collected would help to understand the reasons for the slowness or poor performance because there could be one or several reasons why a system is slow. Slow performance could be due to bad configuration, unoptimized or inappropriately designed code, undersized hardware, or several other reasons. Unless there is unequivocal evidence of why performance is slow, the scientific approach to finding the root cause of the problem should be adopted. The old saying that tuning a computer system is an art may be true when you initially configure a system using a standard set of required parameters suggested by Oracle from the installation guides; but as we go deeper into testing a more scientific approach of data collection, mathematical analysis and reasoning must be adopted because tuning should not be considered a hit-or-miss situation: it is to be approached in a rigorous scientific manner with supporting data.
Problem-solving tasks of any nature need to be approached in a systematic and methodical manner. A detailed procedure needs to be developed and followed from end to end. During every step of the process, data should be collected and analyzed. Results from these steps should be considered as inputs into the next step, which in turn is performed in a similar step-by-step approach. A methodology should be defined to perform the operations in a rigorous manner. Methodology ( a body of methods, rules, and postulates employed by a discipline: a particular procedure or set of procedures ) is the procedure or process followed from start to finish, from identification of the problem to problem solving and documentation. A methodology developed and followed should be a procedure or process that is repeatable as a whole or in increments through iterations.
During all of these steps or iterations, the causes or reasons for a behavior or problem should be based on quantitative analysis and not on guesswork. Every system deployed into production has to grow in the process of a regression method of performance testing to determine poorly performing units of the application. During these tests, the test engineer would measure and obtain baselines and optimize the code to achieve the performance numbers or service-level agreements (SLA) requirements defined by the business analysts.
Performance Requirements
As with any functionality and business rule, performance needs are also (to be) defined as part of business requirements. In organizations that start small, such requirements may be minimal and may be defined by user response and feedback after implementation. However, as the business grows and when the business analyst defines changes or makes enhancements to the business requirements, items such as entities, cardinalities, and the expected response time requirements in use cases should also be defined. Performance requirements are every bit as important as functional requirements and should be explicitly identified at the earliest possible stage. However, too often, the system requirements will specify what the system must do, without specifying how fast it should do it.
When these business requirements are translated into entity models, business processes, and test cases, the cardinalities, that is, the expected instances (aka records) of a business object and required performance levels should be incorporated into the requirements analysis and the modelling of the business functions to ensure these numbers could be achieved. Table is a high-level requirement of a direct-to-home broadcasting system that plans to expand its systems based on the growth patterns observed over the years.
Table 1-1.
Business Requirements
Entity
Current Count
Maximum Count
Maximum Read Access (trans/sec)
Maximum Update Access (trans/sec)
Average Growth Rate (per year)
Smartcards
16,750,000
90,000,000
4,250,000
Products
43,750,000
150,000,000
21,250,000
Transmission logs
400,000 records/day
536,000,000
N/A
670,000,000
Report back files
178,600 records/day
390,000,000 records processed/year
N/A
N/A
550,000,000
Note: trans/sec. = transactions per second; N/A = not applicable.
It will store for 15 million subscriber accounts.
Four smart cards will be stored per subscriber account.
Average growth rate is based on the maximum number of active smart cards.
The peak time for report back transactions is from midnight to 2 AM.
Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Expert Oracle RAC Performance Diagnostics and Tuning»

Look at similar books to Expert Oracle RAC Performance Diagnostics and Tuning. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Expert Oracle RAC Performance Diagnostics and Tuning»

Discussion, reviews of the book Expert Oracle RAC Performance Diagnostics and Tuning and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.