CPU.  Certain operations within the Trace Analyzer are CPU bound (e.g., data filtering and find operations).  Additionally, the Java user interface libraries used presume fairly modern hardware, and may seem sluggish on slower processors.  The impact of a slower processor will be particularly evident when processing very large trace files.

RAM.  The above recommendations are an educated best guess at RAM requirements.  A clear-cut recommendation is difficult to make, as memory utilization is largely dependent upon the implementation of the underlying JVM on different platforms, and is also heavily dependent upon the other processes running in the system.

Disk Space.  The amount of disk space used by Trace Analyzer files may grow very slightly over time, as users add custom reports, filters, aliases, and bookmarks.  However, under normal use, the amount of incremental disk space consumed over time is nearly negligible.

Screen Resolution.  Attempting to run the program at a lower resolution will be confining at best.  At worst, some features may be unavailable at lower resolutions, as the user interface may omit certain controls or components which would not fit in the available screen area.

Color Palette.  If a color palette of fewer than 256 colors is used, images will be distorted and subtle differences in color will be lost, which may be significant to correctly interpreting trace information.