DOCSLIB.ORG

Guide to Openvms Performance Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Guide to Openvms Performance Management Guide to OpenVMS Performance Management Order Number: AA–PV5XA–TE May 1993 This manual is a conceptual and tutorial guide for experienced users responsible for optimizing performance on OpenVMS systems. Revision/Update Information: This manual supersedes the Guide to VMS Performance Management, Version 5.2. Software Version: OpenVMS VAX Version 6.0 Digital Equipment Corporation Maynard, Massachusetts May 1993 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1993. All rights reserved. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ACMS, ALL–IN–1, Bookreader, CI, DBMS, DECnet, DECwindows, Digital, MicroVAX, OpenVMS, PDP–11, VAX, VAXcluster, VAX DOCUMENT, VMS, and the DIGITAL logo. All other trademarks and registered trademarks are the property of their respective holders. ZK4521 This document was prepared using VAX DOCUMENT Version 2.1. Contents Preface ............................................................ ix 1 Introduction to Performance Management 1.1 Knowing Your Workload ....................................... 1–2 1.1.1 Workload Management .................................... 1–3 1.1.2 Workload Distribution ..................................... 1–4 1.1.3 Code Sharing ............................................ 1–4 1.2 Evaluating User Complaints . ................................ 1–5 1.2.1 Recognizing Hardware and MWAIT Problems ................... 1–6 1.2.2 Recognizing Unrealistic Expectations . ....................... 1–7 1.3 Preparing for a Performance Investigation . ....................... 1–7 1.3.1 Understanding What Tuning Is .............................. 1–7 1.3.2 Predicting When Tuning Is Required . ....................... 1–8 1.4 Evaluating Tuning Success .................................... 1–9 1.5 Deciding When To Stop Tuning . ................................ 1–9 1.6 Performance Options for the System Manager ...................... 1–10 2 Review of OpenVMS Resource Management 2.1 OpenVMS Memory Management Analogy . ....................... 2–1 2.2 Advanced Memory Management Mechanisms and Policies ............ 2–6 2.2.1 Automatic Working Set Adjustment ........................... 2–6 2.2.1.1 Working Set Sizes ..................................... 2–12 2.2.1.2 Initial Working Set Limits and Characteristics ............... 2–13 2.2.1.3 Adjustments to AWSA Parameters . ....................... 2–14 2.2.1.4 Performance Management Strategies and Automatic Working Set Adjustment . ........................................ 2–15 2.2.2 Swapper Trimming ........................................ 2–16 2.2.3 Virtual Balance Slots ...................................... 2–18 2.2.4 Proactive Reclamation of Memory from Idle Processes ............ 2–19 2.2.4.1 How Is This Policy Enabled? ............................. 2–19 2.2.4.2 Reclaiming Memory from Long-Waiting Processes ............. 2–20 2.2.4.3 Reclaiming Memory from Periodically Waking Processes . ....... 2–21 2.2.5 Memory Sharing . ........................................ 2–21 2.2.6 OpenVMS Scheduling ..................................... 2–25 iii 3 Managing System Resources 3.1 Evaluation Ground Rules . .................................... 3–2 3.2 Collecting and Interpreting Image-Level Accounting Data . ........... 3–3 3.3 Maintaining and Interpreting MONITOR Summaries ................ 3–6 3.4 Understanding System Responsiveness ........................... 3–8 3.4.1 Evaluating Responsiveness of System Resources ................. 3–8 3.4.2 Improving Responsiveness of System Resources ................. 3–9 3.5 Understanding the CPU Resource . ............................ 3–9 3.5.1 Evaluating CPU Responsiveness . ............................ 3–9 3.5.1.1 Compute Queue . .................................... 3–9 3.5.1.2 Estimating Available CPU Capacity ........................ 3–11 3.5.1.2.1 Voluntary Wait States . ............................ 3–11 3.5.1.2.2 Involuntary Wait States . ............................ 3–12 3.5.2 Improving CPU Responsiveness . ............................ 3–13 3.5.2.1 Equitable CPU Sharing ................................. 3–13 3.5.2.2 Reduction of CPU Consumption by the System ............... 3–14 3.5.2.2.1 Interpreting MONITOR MODES Data ................... 3–15 3.5.2.3 CPU Offloading . .................................... 3–18 3.5.2.4 CPU Offloading Between Processors on the Network ........... 3–19 3.5.2.5 CPU Load Balancing in a VAXcluster . ................... 3–19 3.6 Understanding the Memory Resource ............................ 3–20 3.6.1 Evaluating Memory Responsiveness .......................... 3–23 3.6.1.1 Page Faulting ......................................... 3–23 3.6.1.1.1 Secondary Page Cache . ............................ 3–24 3.6.1.2 Swapping and Swapper Trimming ......................... 3–25 3.6.2 Improving Memory Responsiveness ........................... 3–26 3.6.2.1 Equitable Memory Sharing . ............................ 3–26 3.6.2.2 Reduction of Memory Consumption by the System . ........... 3–27 3.6.2.3 Memory Offloading . .................................... 3–28 3.6.2.4 Memory Load Balancing ................................ 3–29 3.7 Understanding the Disk I/O Resource ............................ 3–29 3.7.1 Components of a Disk Transfer . ............................ 3–30 3.7.2 Disk Capacity and Demand ................................. 3–30 3.7.2.1 Seek Capacity ........................................ 3–30 3.7.2.2 Data Transfer Capacity ................................. 3–30 3.7.2.3 Demand . ............................................ 3–31 3.7.3 Evaluating Disk I/O Responsiveness .......................... 3–31 3.7.4 Improving Disk I/O Responsiveness ........................... 3–33 3.7.4.1 Solid-State Disks . .................................... 3–33 3.7.4.2 Equitable Disk I/O Sharing . ............................ 3–34 3.7.4.3 Reduction of Disk I/O Consumption by the System . ........... 3–34 3.7.4.3.1 Paging I/O Activity ................................. 3–34 3.7.4.3.2 Swapping I/O Activity . ............................ 3–35 3.7.4.3.3 File System (XQP) I/O Activity ........................ 3–35 3.7.4.4 Disk I/O Offloading .................................... 3–37 3.7.4.4.1 Using the Virtual I/O Cache ........................... 3–37 3.7.4.4.2 Using a RAM Disk .................................. 3–39 3.7.4.4.3 Other Disk I/O Offloading Techniques ................... 3–40 3.7.4.5 Disk I/O Load Balancing ................................ 3–41 3.8 Summary of Important MONITOR Data Items . ................... 3–42 iv 4 Diagnosing Resource Limitations 4.1 Diagnostic Strategy . ........................................ 4–1 4.2 Isolating Memory Limitations . ................................ 4–4 4.2.1 Analyzing the Excessive Page Faulting Symptom . ............... 4–4 4.2.1.1 Image Activations Are Excessive . ....................... 4–5 4.2.1.2 Characterizing Hard Versus Soft Faults .................... 4–6 4.2.1.3 Total Working Set Size Is Too Small—Overview of the Problem . 4–7 4.2.1.4 WSDEFAULT, WSQUOTA, and WSEXTENT Values Are Inappropriate . ........................................ 4–10 4.2.1.5 Borrowing Is Ineffective . ................................ 4–11 4.2.1.6 AWSA Might Be Disabled ............................... 4–11 4.2.1.7 AWSA Is Ineffective—Overview ........................... 4–11 4.2.1.8 Swapper Trimming Is Too Vigorous . ....................... 4–13 4.2.2 Analyzing the Swapping Symptom ............................ 4–14 4.2.3 Detecting Harmful Swapping ................................ 4–15 4.2.4 Investigating Why Processes Consume Unreasonable Amounts of Memory ................................................ 4–16 4.2.4.1 Large, Compute-Bound Process Gains Inordinate Control of Memory ............................................. 4–19 4.2.4.2 Large Waiting Process Is Never Outswapped . ............... 4–20 4.2.4.3 Too Many Processes Compete for Available Memory ........... 4–20 4.2.4.4 Borrowing Is Too Generous .............................. 4–21 4.2.4.5 Swapper Trimming Is Ineffective . ....................... 4–21 4.2.4.6 Many Working Sets Are Too Large . ....................... 4–21 4.2.4.7 Disk Thrashing Occurs . ................................ 4–22 4.2.4.8 System Swaps Rather Than Pages . ....................... 4–23 4.2.4.9 Demand Exceeds Available Memory . ....................... 4–23 4.2.5 Analyzing the Limited Free Memory Symptom . ............... 4–23 4.3 Isolating I/O Limitations ...................................... 4–24 4.3.1 Disk or Tape Operation Problems (Direct I/O) ................... 4–24 4.3.2 Determining I/O Rates ..................................... 4–25 4.3.2.1 Device I/O Rate Is Below Capacity . ....................... 4–25 4.3.2.2 Direct I/O Rate Is Abnormally High . ....................... 4–27 4.3.2.3 Disk Activity Is Due to Paging or Swapping . ............... 4–29 4.3.3 Reduce I/O Demand or Add Capacity . ......................
Load more

Recommended publications
  • Openvms Record Management Services Reference Manual
    OpenVMS Record Management Services Reference Manual Order Number: AA-PV6RD-TK April 2001 This reference manual contains general information intended for use in any OpenVMS programming language, as well as specific information on writing programs that use OpenVMS Record Management Services (OpenVMS RMS). Revision/Update Information: This manual supersedes the OpenVMS Record Management Services Reference Manual, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, PATHWORKS, DECnet, DEC, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
    [Show full text]
  • Overcoming Traditional Problems with OS Huge Page Management
    MEGA: Overcoming Traditional Problems with OS Huge Page Management Theodore Michailidis Alex Delis Mema Roussopoulos University of Athens University of Athens University of Athens Athens, Greece Athens, Greece Athens, Greece [email protected] [email protected] [email protected] ABSTRACT KEYWORDS Modern computer systems now feature memory banks whose Huge pages, Address Translation, Memory Compaction aggregate size ranges from tens to hundreds of GBs. In this context, contemporary workloads can and do often consume ACM Reference Format: Theodore Michailidis, Alex Delis, and Mema Roussopoulos. 2019. vast amounts of main memory. This upsurge in memory con- MEGA: Overcoming Traditional Problems with OS Huge Page Man- sumption routinely results in increased virtual-to-physical agement. In The 12th ACM International Systems and Storage Con- address translations, and consequently and more importantly, ference (SYSTOR ’19), June 3–5, 2019, Haifa, Israel. ACM, New York, more translation misses. Both of these aspects collectively NY, USA, 11 pages. https://doi.org/10.1145/3319647.3325839 do hamper the performance of workload execution. A solu- tion aimed at dramatically reducing the number of address translation misses has been to provide hardware support for 1 INTRODUCTION pages with bigger sizes, termed huge pages. In this paper, we Computer memory capacities have been increasing sig- empirically demonstrate the benefits and drawbacks of using nificantly over the past decades, leading to the development such huge pages. In particular, we show that it is essential of memory hungry workloads that consume vast amounts for modern OS to refine their software mechanisms to more of main memory. This upsurge in memory consumption rou- effectively manage huge pages.
    [Show full text]
  • Oracle Database Installation Guide 10G Release 2 (10.2)
    Oracle®[1] Database Installation Guide 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 June 2015 Oracle Database Installation Guide, 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 Copyright © 2008, 2015, Oracle and/or its affiliates. All rights reserved. Primary Author: Nisha Sridhar Contributors: Dave Hayter, Gary Huffman, Marc Noel, Chris Schuetz, David Miller, Kevin Duffy, Steve Holck, Grant Hayden, Gary Tate This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Asynchronous Page Faults Aix Did It Red Hat Author Gleb Natapov August 10, 2010
    Asynchronous page faults Aix did it Red Hat Author Gleb Natapov August 10, 2010 Abstract Host memory overcommit may cause guest memory to be swapped. When guest vcpu access memory swapped out by a host its execution is suspended until memory is swapped back. Asynchronous page fault is a way to try and use guest vcpu more efficiently by allowing it to execute other tasks while page is brought back into memory. Part I How KVM Handles Guest Memory and What Inefficiency it Has With Regards to Host Swapping Mapping guest memory into host memory But we do it on demand Page fault happens on first guest access What happens on a page fault? 1 VMEXIT 2 kvm mmu page fault() 3 gfn to pfn() 4 get user pages fast() no previously mapped page and no swap entry found empty page is allocated 5 page is added into shadow/nested page table What happens on a page fault? 1 VMEXIT 2 kvm mmu page fault() 3 gfn to pfn() 4 get user pages fast() no previously mapped page and no swap entry found empty page is allocated 5 page is added into shadow/nested page table What happens on a page fault? 1 VMEXIT 2 kvm mmu page fault() 3 gfn to pfn() 4 get user pages fast() no previously mapped page and no swap entry found empty page is allocated 5 page is added into shadow/nested page table What happens on a page fault? 1 VMEXIT 2 kvm mmu page fault() 3 gfn to pfn() 4 get user pages fast() no previously mapped page and no swap entry found empty page is allocated 5 page is added into shadow/nested page table What happens on a page fault? 1 VMEXIT 2 kvm mmu page fault() 3 gfn to pfn()
    [Show full text]
  • What Is an Operating System III 2.1 Compnents II an Operating System
    Page 1 of 6 What is an Operating System III 2.1 Compnents II An operating system (OS) is software that manages computer hardware and software resources and provides common services for computer programs. The operating system is an essential component of the system software in a computer system. Application programs usually require an operating system to function. Memory management Among other things, a multiprogramming operating system kernel must be responsible for managing all system memory which is currently in use by programs. This ensures that a program does not interfere with memory already in use by another program. Since programs time share, each program must have independent access to memory. Cooperative memory management, used by many early operating systems, assumes that all programs make voluntary use of the kernel's memory manager, and do not exceed their allocated memory. This system of memory management is almost never seen any more, since programs often contain bugs which can cause them to exceed their allocated memory. If a program fails, it may cause memory used by one or more other programs to be affected or overwritten. Malicious programs or viruses may purposefully alter another program's memory, or may affect the operation of the operating system itself. With cooperative memory management, it takes only one misbehaved program to crash the system. Memory protection enables the kernel to limit a process' access to the computer's memory. Various methods of memory protection exist, including memory segmentation and paging. All methods require some level of hardware support (such as the 80286 MMU), which doesn't exist in all computers.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • Openvms Security
    OpenVMS Security Presented by Paul Williams PARSEC Group 999 18th Street, Suite 1725 Denver, CO 80202 www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/openvmssecurity.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • OpenVMS Security Design • Physical Security • Object Security • UIC/ACL Security • User Access • Break-in Detection • Network and Internet Considerations • Encrypted Network Communication • Kerberos • Secure Socket Layer (SSL) Goals • Discuss the important points and consideration of OpenVMS Security • Concentrate on the mechanics and mechanisms of OpenVMS features. • Show how OpenVMS is one of the most secure operating systems on the market. OpenVMS Security Design • Security was designed into OpenVMS since V1.0 • Many different levels of security in OpenVMS Physical Security Object Security User Management Network Security • Has never had a virus Physical Security • System • System Console • Storage devices and media System Disk Data and Database Volumes Backups • Network devices and media Physical Security: System • Increase system reliability through restricted access Prevent intentional tampering and outage Prevent outage due to accidents • Prevent Front Panel Access Halts Reset/initializations Power switch/source Power on action settings (VAX) switch Physical Security: Console • Can be a big security hole for OpenVMS Anyone with physical access to the console can break into OpenVMS buy getting into the SYSBOOT utility. Then OpenVMS can be broken into: Buy redirecting startup Buy changing system parameters Physical Security: Getting to SYSBOOT on the Integrity Console Example • On the Integrity shutdown to the EFI Boot Manager and select the EFI Shell and create a alias.
    [Show full text]
  • Measuring Software Performance on Linux Technical Report
    Measuring Software Performance on Linux Technical Report November 21, 2018 Martin Becker Samarjit Chakraborty Chair of Real-Time Computer Systems Chair of Real-Time Computer Systems Technical University of Munich Technical University of Munich Munich, Germany Munich, Germany [email protected] [email protected] OS program program CPU .text .bss + + .data +/- + instructions cache branch + coherency scheduler misprediction core + pollution + migrations data + + interrupt L1i$ miss access + + + + + + context mode + + (TLB flush) TLB + switch data switch miss L1d$ +/- + (KPTI TLB flush) miss prefetch +/- + + + higher-level readahead + page cache miss walk + + multicore + + (TLB shootdown) TLB coherency page DRAM + page fault + cache miss + + + disk + major minor I/O Figure 1. Event interaction map for a program running on an Intel Core processor on Linux. Each event itself may cause processor cycles, and inhibit (−), enable (+), or modulate (⊗) others. Abstract that our measurement setup has a large impact on the results. Measuring and analyzing the performance of software has More surprisingly, however, they also suggest that the setup reached a high complexity, caused by more advanced pro- can be negligible for certain analysis methods. Furthermore, cessor designs and the intricate interaction between user we found that our setup maintains significantly better per- formance under background load conditions, which means arXiv:1811.01412v2 [cs.PF] 20 Nov 2018 programs, the operating system, and the processor’s microar- chitecture. In this report, we summarize our experience on it can be used to improve high-performance applications. how performance characteristics of software should be mea- CCS Concepts • Software and its engineering → Soft- sured when running on a Linux operating system and a ware performance; modern processor.
    [Show full text]
  • Getting Even More Grip on Your Security with Pointsecure Or
    OpenVMS and Security getting even more grip on your security with Pointsecure or NDC Gerrit Woertman VSI Professional Services Alliance member VSI OpenVMS trainer EMEA & VSI OpenVMS Ambassador [email protected] www.vmsconsultancy.com Agenda • OpenVMS and Security • EU security laws to report security issues • Non‐HPE/VSI Security packages • Pointsecure – PointAudit – System Detective • Networking Dynamics Corporation (NDC) – Peek & Spy – KEY Capture – Assassin • Questions OpenVMS and Security ‐ 1 • OpenVMS – secure by design • No viruses • One of the first to become US DoD C2‐rating • Declared “Cool and Unhackable” at 2001 DefCon9 as described in 4AA0‐2896ENW.pdf (HP, 11/2005) Alpha OpenVMS with the help of Pointsecure System Detective OpenVMS and Security ‐ 2 • OpenVMS has got optional security solutions – OpenSSL (Secure Socket Layer) https://www.openssl.org/ – Common Data Security Architecture (CDSA) – Kerberos • Everything fine? Seems so, but there is still need for more and better implementation – On VSI’s research list OpenVMS and Security – 3 • OpenVMS ‐ Linux – Windows • With 100% OpenVMS no problems – fine – That’s not real; today’s softwarestacks complex – Splendid isolation? • OpenSource – is that safe? ? OpenVMS and Security – 4 • From http://vmssoftware.com/products.html Unmatched Security Compare OpenVMS' security vulnerability record against other operating systems at CVE Details: http://www.cvedetails.com. The following are direct links to reports for OpenVMS, Linux and Windows: • OpenVMS http://www.cvedetails.com/product/4990/HP‐Openvms.html?vendor_id=10
    [Show full text]
  • Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API
    Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API Release 7.0 Part No. A41981-1 ® Guide to Using the Oracle SQL/Services Client API Release 7.0 Part No. A41981-1 Copyright © 1993, 1996, Oracle Corporation. All rights reserved. This software contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use, duplication and disclosure of the programs shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the programs shall be subject to the restrictions in FAR 52.227-14, Rights in Data—General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the programs.
    [Show full text]
  • Virtual Memory §5.4 Virt Virtual Memory U Al Memo Use Main Memory As a “Cache” For
    Chapter 5 Large and Fast: Exppgloiting Memory Hierarchy Part II Virtual Memory §5.4 Virt Virtual Memory u al Memo Use main memory as a “cache” for secondary (disk) storage r y Managed jointly by CPU hardware and the operating system (OS) Programs share main memory Each gets a private virtual address space holdinggqy its frequently used code and data Protected from other programs CPU and OS translate virtual addresses to physical addresses VM “block” is called a page VM translation “miss” is called a page fault Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 2 Address Translation Fixed-size pages (e.g., 4K) Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 3 Page Fault Penalty On page fault, the page must be fetched from disk Takes millions of clock cycles Handled by OS code Try to minimize page fault rate Fully associative placement Smart replacement algorithms Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 4 Page Tables Stores placement information Array of page table entries, indexed by virtual page number Page table register in CPU points to page table in physical memory If page is present in memory PTE stores the physical page number Plus other status bits (referenced, dirty, …) If page is not present PTE can refer to location in swap space on dis k Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 5 Translation Using a Page Table Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 6 Mapping Pages to Storage Chapter 5 — Large and Fast: Exploiting Memory Hierarchy — 7 Replacement and Writes
    [Show full text]