Amount of measured methods:

• The freeware version is for small projects and private use and can measure until 30 methods.
• The professional version is for large projects and industry use and can measure until 10000 methods.

Conditional compilation:
Fully supported. Compiler symbols and switches are read from the compilers option file (DOF).

Customer suggestions:
Many customer suggestions have been implemented in ProDelphi in the last two versions.

Exclusion of parts of the program from measuring:
Units or Include files:

• Don't copy the unit into the profiling directory,
• Set the write protection for the units file
• Insert a statement to the start of the unit file

• Insert a statement before and after the part, that shall not be measured.

• Procedures, that are called at least 10 times and consume less than 1µs per call, can automatically be excluded from measurement.

Local Procedures:
Fully supported.

Measurement accuracy:
ProDelphi is measuring very accurately. The measurement overhead is automatically removed from the measured times. A sophisticated algorithym calculates the runtime used for measurement at initialization time. You can easily check the accuracy of ProDelphi by downloading the profiler tester. It consists of two programs: One, so to say, manually measures the run-time of a few procedures and displays the result. The second program is the same without measuring, it has to be profiled. Compare the real runtime with the measurement result of ProDelphi.

Measuring programs with threads:
Supported, but with less accuracy.

Measuring runtimes in DLL's:
Fully supported

Online operating the measurement:
Measurement can be switched on and off at the programs runtime, also results can be stored online. This speeds up the opimization process.

Object orientation:
Specially supported by the feature of adding the runtimes of all methods with the same name (if the used object is the same).
Example: A method 'LoadFromDisk' calls the method 'LoadFromDisk' of the inherited class. In this case the runtimes of both classes will be added.

Programming-API:
Measurement can be switched on and off at runtime. Intermediate results can be stored on disk.

Security:
It is strongly recommended to copy all sources into a special profiling directory. ProDelphi inserts statements into the source files. If this process has a bug or in case of power failure, the sources might be destroyed. This is the reason why ProDelphi does not use the IDE-directory path.

Switching on and off of measurement:
Simply done by deleting a compiler symbol and recompilation. At runtime this is also possible by the online operation window. Also intermediate measurement results can be stored at runtime (see also Programming-API).

Upgrading:
If you decide to use ProDelphi, you can download any upgrade or bug fix from my homepage. If you need ProDelphi for a larger project and 20 measured procedures are not enough for you, you can oder the professional version via ShareIt registration service. If you do so, you also can download new versions from my homepage for free. They will automatically run as professional version. (Buy one - get many).

Viewing of measurement results:
Results can be either displayed in CPU-cycles or in 0.1µs-units.
ProDelphi has THREE possibilities of viewing the measured runtimes:

• Built-in viewer and browser (navigator).

The results can be sorted after different criteria. Procedures which consume the most CPU-cycles are filtered and sorted already.
The browser can be used to quickly find a certain method.
Also a text search is implemented.
• ASCII output, ready for printout with Delphi.

This output has a part for all methods + a part for the most CPU-cycle consuming methods.
• Data base export.

Visit authors homepage