Optionally, the Intel® Trace Collector can save trace data in the indexed tracefile format (ITF). This is an experimental feature. The ITF was developed to provide direct access to particular tracefile records instead of tracefile chunks as the existing STF anchors do. An ITF file has the block-oriented structure where blocks are linked together forming a multi-branch index/data trees separated by processes, threads, and event types. Each record type has a fixed size, which allows the Intel® Trace Collector to easily jump to any particular record in the file. The Intel® Trace Collector supports the following two access modes:
Sequential access: block-by-block, record-by-record (as regular STF reader does). This access mode is used by existing regular tracefile readers (for example, Intel® Trace Analyzer or stftool).
Direct access: using a key (for example, time stamp or event number). This access mode is used by Intel® Trace Analyzer to implement the seek and jump function.
For the first experimental version, the ITF is integrated into the existing STF file structure. Main .stf file, declaration and statistics files (.dcl/.sts) are the same as in case of regular STF; event files (.cop, .msg, .f, .i, .s, .c, .r) are stored in ITF.
To select this format, specify the ITFLOGFILE configuration directive (--itflogfile stftool option), which is useful only in combination with the LOGFILE-FORMAT STF directive.