Deconstructing the Log File
This section looks in more detail at each part of an FME log.
| Jake Speedie says... |
| Being able to interpret a log file is vital for performance tuning. If you can’t understand what FME is doing, then there isn’t much chance you’ll be able to improve upon it! |
The overall structure of an FME log is approximately four different sections.
- Command-line statement
- Configuration and setup information
- The translation and transformation itself
- A summary of the translation
Command Line Statement
At the very top of a log file appears the command line statement. This is the command that FME Workbench is using to run the translation:
In terms of performance, this section doesn’t tell us much. However, it is useful to confirm which instance of FME is running, particularly when you have several versions installed. Note that the version number in the above image is merely where FME is installed; it's not necessarily the version number that's running.
This section also tells us what published parameters are in the workspace and what their values are.
Perhaps the most useful part of this section is that you can copy and paste this statement to run the workspace through a command line or using a batch file.