This document provides a quick introduction to profiling code using the Xdebug profiler Cachegrind. It discusses evaluating performance per function by looking at metrics like execution time, cumulative time, and number of calls. It also covers evaluating code flow and tips for using Cachegrind, including enabling it in the PHP config file and a MastersPortal configuration. The document recommends using a regex expression to filter functions when first looking at the overall profiling data and walking through functions to check for expected self and cumulative times and number of calls.

1. Cachegrind 101 A quick introduction into profiling

3. Amount of ms

4. Cumulative amount of ms

5. Nr of calls

6. Evaluating your code flow2 What is Cachegrind?

7. PHP config file: xdebug.profiler_enable=1 xdebug.profiler_output_dir="D:achegrindquot; xdebug.profiler_output_name="cachegrind.out.%t-%p-%s.txt" MastersPortal configuration: Enable template cache: <template> <template_cache>true</template_cache> </template> 3 Getting started

8. Before looking at the Overall tab, use the regex expression ^[^T4T] Walk through your function, starting at its call and check if: Self times are in line with the amount of code in it Cumulative times do not show major peaks Functions are called according to expectations Getters, setters and other quick functions are not called ridiculously often Total time !== real execution time 4 Tips

9. Happy Grinding! 5