Skip to main contentSkip to search
Powered by Zoomin Software. For more details please contactZoomin
Progress DocumentationProgress Documentation
Progress Documentation
  • Home
  • Home
  • EnglishČeštinaDeutsch (Germany)Español (Spain)ФранцузскийItaliano (Italy)Português (Brasil)日本語Русский (Russia)中文 (简体) (China)中文 (繁體, 台灣) (Taiwan)ar-AR
  • Login

OpenEdge Database Essentials

Profile your system performance

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
Table of Contents
  • Introduction to Databases
    • Advantages of a database
    • Elements of a relational database
      • Tables
      • Rows
      • Columns
      • Keys
      • Indexes
    • Apply the principles of the relational model
    • OpenEdge database and the relational model
      • Database schema and metaschema
      • Sports 2020 database
    • Key points to remember
  • Database Design
    • Design basics
    • Data analysis
    • Logical database design
    • Table relationships
      • One-to-one relationship
      • One-to-many relationship
      • Many-to-many relationship
    • Normalization
      • First normal form
      • Second normal form
      • Third normal form
      • Denormalization
    • Define indexes
      • Indexing basics
        • How indexes work
        • Reasons for defining an index
        • Sample indexes
        • Disadvantages of defining an index
      • Choose which tables and columns to index
      • Indexes and ROWIDs
      • Calculate index size
      • Eliminate redundant indexes
      • Deactivate indexes
    • Physical database design
  • OpenEdge RDBMS
    • OpenEdge database file structure
      • Other database-related files
    • OpenEdge architecture
      • Storage areas
        • Control area
        • Schema area
        • Primary recovery area
        • Application data area
        • After-image area
        • Encryption Policy area
        • Audit data and index areas (optional)
        • Transaction log area
      • Guidelines for choosing storage area locations
      • Extents
      • Clusters
      • Blocks
        • Data blocks
        • Index blocks
      • Other block types
        • Master blocks
        • Storage object blocks
        • Free blocks
        • Empty blocks
    • Storage design overview
      • Map objects to areas
    • Determine configuration options
      • System platform
      • Connection modes
        • Single-user mode
        • Multi-user mode
        • Batch mode
        • Interactive mode
      • Client type
        • Self-service clients
        • Network clients
      • Database location
      • Database connections
    • Relative- and absolute-path databases
  • Administrative Planning
    • Data layout
      • Calculate database storage requirements
        • Formulas for calculating field storage
        • Sample to estimate storage requirements
        • Database-related size criteria
      • Size your database areas
        • Block sizes
        • Specify records per block
        • Example of calculating records per block
        • Unused slots
        • Determine space to allocate per area
        • Distribute tables across storage areas
        • Use extents
        • Index storage
        • Primary recovery area
    • Database areas
      • Data area optimization
        • Split off schema
        • Choose an appropriate block size
        • Keep extents sized to eliminate I/O indirection
        • Keep areas small for offline utilities
        • Always have an overflow extent for each area
        • Enable large files
        • Partition data
      • Primary recovery (before-image) information
        • Extent size rules
        • Sequential access
        • BI grow option
      • After-image information
        • Always use multi-volume extents
        • Isolate for disaster recovery
        • Sizing after-image extents
    • System resources
    • Disk capacity
      • Disk storage
        • Understand data storage
        • Determine data storage requirements
        • Determine current storage using operating system commands
      • Project future storage requirements
        • Examine your growth pattern
        • Move archival data off the production machine
      • Compare expensive and inexpensive disks
      • Understand cache usage
      • Increase disk reliability with RAID
      • OpenEdge in a network storage environment
      • Disk summary
    • Memory usage
      • Estimate memory requirements
        • Operating system memory estimates
        • Understand memory internals
        • OpenEdge-specific memory estimates
        • Example memory budget
      • Optimize memory usage
        • Buffer hits
        • Increase memory
        • Decrease memory
        • Direct IO
        • Private buffers (-Bp)
        • Alternate Buffer Pool
    • CPU activity
      • Tune your system
        • CPU usage and the -spin parameter
      • Understand idle time
      • Fast CPUs versus many CPUs
    • Tunable operating system resources
  • Database Administration
    • Database administrator role
      • Security administrator role
    • Ensure system availability
      • Database capacity
      • Application load
      • System memory
      • Additional factors to consider in monitoring performance
      • Test to avoid problems
    • Safeguard your data
      • Why backups are done
      • Create a complete backup and recovery strategy
        • Who does the backup?
        • What does the backup contain?
        • Where does the backup go?
        • How to label a backup
        • When do you do a backup?
      • Use PROBKUP versus operating system utilities
        • Understand the OpenEdge PROBKUP utility
        • How PROBKUP works
        • Add operating system utilities to augment PROBKUP
      • After-imaging implementation and maintenance
        • OpenEdge Replication
      • Test your recovery strategy
    • Maintain your system
    • Daily monitoring tasks
      • Monitor the database log file
        • Key Events
      • Monitor area fill
      • Monitor buffer hit rate
      • Monitor buffers flushed at checkpoint
      • Monitor system resources (disks, memory, and CPU)
    • Periodic monitoring tasks
      • Database analysis
      • Rebuild indexes
      • Compact indexes
      • Fix indexes
      • Move tables
      • Move indexes
      • Truncate and grow BI files
      • Dump and load
        • Data Dictionary dump and load
        • Bulk loader
        • Binary dump and load
    • Periodic event administration
      • Annual backups
      • Archiving
      • Modify applications
        • Make schema changes
        • Make application code changes
      • Migrate OpenEdge releases
    • Profile your system performance
      • Establish a performance baseline
        • Collect your baseline statistics
        • Understand your results
      • Performance tuning methodology
    • Summary
Table of Contents

Profile your system performance

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
Print
  • Last Updated: February 11, 2026
  • 1 minute read
    • OpenEdge
    • Version 13.0
    • Documentation

Performance is a matter of perception. Users may say performance is slow or fast based on many factors. It is best to take perception out of the equation by establishing some baselines on important aspects of your system.

Contents
  • Establish a performance baseline
  • Performance tuning methodology
TitleResults for “How to create a CRG?”Also Available inAlert