# Overview

The overview part of the profile form shows an overview of all the file events on a per "path" basis. We say per "path" because the files are uniquely identified based on the device, the archive and the file name. For example: A file with device `C:`, archive `archive.big` and file `file.dat` represents a unique combination for that path. Another file with device `D:`, archive `archive.big` and file `file.dat` is not the same entry as the devices differ.

The overview part contains a number of columns:

- Start time
- End time
- Delta time
- Type
- Tag1
- Device1
- Archive2
- File
- Seek time
- Inter seek time
- Intra seek time
- Read time
- Write time1
- Actual time
- Delay time
- Idle time
- Read size
- Write size1
- Read duplicate
- Write duplicate1
- Avg. Read throughput
- Avg. Write throughput1

1) Only Simple profiler data supports this.
2) Only Simple profiler data in combination with RwBigFile or RTAM supports this.

Start time is the time of the first file event for the given file.

End time is the time of the last file event for the given file.

Delta time is the time different between the last file event and the first file event for the given file (End time - Start time).

Type is the type of operation that occurred 1. For example: `READ`, `WRITE` or `OPEN`.

Tag shows the tag that was set in the code. This can be used in the code (using `SetTag`) so that you can track the different phases of the loading of data1. By default this is set to `NONE`

Device shows the device for which the file was loaded1. For example: `bdvd:`. This can be used to figure out which files are used from from

Archive shows the BIG file from which the file originated. This also includes memory mapped big files. Note: You need RwBigFile 1.02 or newer for this to work2.)

File is the file name of the file for which the operation occurred. Note: in order to use the filenames within archives you will need to use RwBigFile or RTAM2. Note: when using XBOX 360 profile data this may actually contain 2 separate filenames, separated by a comma, because of a limitation of the emulator tool.

Seek time shows the time it took all the seek operations on this file (in milliseconds.) This is only the seek time that resulted from the reads/writes, so any seeks done manually in the code are ignored in this.

Inter seek time shows the amount of inter seek time (in milliseconds.) Inter seek time is the amount of time for seeks between different files.

Intra seek time shows the amount of intra seek time (in milliseconds.) Intra seek time is the amount of time for seeks within a file.

Read time shows the time it took all the read operations on this file (in milliseconds.)

Actual time shows the time it took the file system to actually perform the operation. If the file system had no overhead at all then the formula for actual time would be `actual time = read time + seek time`. However the file system always has some overhead so there is some extra time spent here. This extra time is called delay time.

Delay time shows the extra amount of time that the file system took. The formula for delay time becomes `delay time = actual time - read time - seek time`

Idle time shows the time the device was idle (in milliseconds). The idle time is mainly indicating some form of processing going on after the data has been read from the file. The formula for idle time is `idle time = start time - (previous start time - actual time)`

Read size shows the size of the read operation (in bytes.)

Write size shows the size of the write operation (in bytes.)

Read Duplicate shows the amount of duplicate bytes of the read operations.

Write Duplicate shows the amount of duplicate bytes of the write operations.

Avg. Read throughput shows the (estimated average) throughput of the read operation. Sometimes this is far higher than the hardware’s theoretical maximum. This can happen because the hardware cached future reads, so the next read will be high speed. In general it is more important to try to find the low throughput numbers and improve those files.

Avg. Write throughput shows the (estimated average) throughput of the write operation. Sometimes this is far higher than the hardware’s theoretical maximum. This can happen because the hardware cached future reads, so the next read will be high speed. In general it is more important to try to find the low throughput numbers and improve those files.

The columns that are displayed can be customized by `right-clicking` on the control. This will show a context menu:

This context menu allows you to select which columns are displayed. Also the context menu contains an option to `Auto size` the columns, which makes the columns just wide enough so that the data fits perfectly.

Tip: If you do not like the order of the columns you can drag the column headers to another location.

Feedback? Please provide us with your comments on this topic.
For more help, send us an email
© 2007 Electronic Arts. All rights reserved.