This section provides a comprehensive glossary of terms related to the OpenEdge Memory Profiler tool.

  • Memory profiler—Another term for Progress® OpenEdge® Memory Profiler.
  • Memory Profiling—Collecting a series of snapshots of memory consumption by an OpenEdge application over time.
  • Snapshot—An image of metrics tracked by the ABL Virtual Machine (AVM) for a running OpenEdge application at a specific time and with a specific identification tag.
  • Recording—A series of snapshots representing captured memory use metrics over time. A recording is also referred to as memory profiling recording. A physical file consisting of a recording is called a recording file. The file extension of the memory profile recording is .oemp, which stands for OpenEdge Memory Profiler. A recording file is also referred to as memory profile recording file.

    For more information, see Memory profile recording.

  • Watched directory—The location where the recording file is stored. Any newly uploaded files, as well as those placed directly in this location, may be read and processed for possible import.
    Note: The default watched directory for the OpenEdge Memory Profiler application is the import folder located in the <WRKDIR>\oemp\ directory, and it is scanned for reading and importing the recordings.
  • Header—An identifier in the recording that provides the recording meta-data. For more information about the header, see Recordings.
  • Import—Involves parsing and ingesting recording data from a source, which processes each accessible snapshot into tables within the relational database management system (RDBMS) for analysis. The tool displays these snapshots that you can visualize to identify and analyze memory leaks. For the purpose of OpenEdge Memory Profiler, import is also known as processing.
    Note: Progress recommends using smaller, distinct recordings for more effective analysis of memory utilization during application execution. This approach helps isolate behavior and makes it easier to investigate specific areas of code for improper memory utilization. For recording files larger than 1 GB, or files which contain a large number of objects or snapshots, the processing time may increase, affecting performance across all pages, including graphs, snapshots, and other visualizations.
  • Object—In an OpenEdge application, the term object encompasses any type of element that holds memory. While some elements explicitly include object in their name, such as ABL Objects, others, like procedures, do not. Despite this, all such elements are collectively referred to as objects in a broader sense.