User Guide > Using Engine Profiler > File Format of the Profile Output File
Was this helpful?
File Format of the Profile Output File
This topic describes the format of the profile output file. All strings and numbers are stored in the Java binary format. Numbers (2-byte integer, 4-byte integer, and 8-byte IEEE floating point) are all stored MSB first. Strings are stored as a two-byte number of bytes, followed by the string itself encoded as UTF-8.
The general format of the file is:
• Question: The header of the file starts with a “magic” string DJPROF. This is not a Java string, but six characters of the string. Following this is a two-byte integer containing the version number of the file (currently, the version is 1). After the version number is a profile count that indicates the total time the profiling was active.
• Node info blocks: This section starts with a four-byte integer containing the number of node information entries to follow. Each node entry consists of a four-byte integer representing the node type.The following table provides the current values and their representative components:
Value
Component
0
Module (code module, map expression, and so on.)
1
User-defined function
2
External (DLL) function
3
Built-in function
A string displaying the name of the node.
Profile count for the node that indicates the total time spent on the node.
Possible node-type specific data:
– Code module (type 0): a string that indicates the actual code of the module.
– User-defined function (type 1): an unsigned two-byte integer that indicates the (0-based) number of the code module where the function is defined.
• Graph info blocks
There are a number of places where a profile count is written. This simply refers to an unsigned four-byte integer number of iterations, followed by a double representing the number of seconds.
 
Last modified date: 10/22/2024