Changes

Jump to: navigation, search

SPO600 Profiling Lab

645 bytes added, 09:33, 4 October 2018
no edit summary
[[Category:SPO600 Labs- Retired]]{{Admon/lab|Purpose of this Lab|In this lab, you will do a build of a software package with profiling enabled, execute the program, and analyze the data produced by the profiling system to find potential places for optimization in the software.}}{{Admon/important|This lab is not a required lab in the current semester of the SPO600 course.|Please refer to the other labs in the [[:Category:SPO600 Labs|SPO600 Labs]] category.}}== Optional Lab 3 ==
=== Prerequisites ===
#* Perl
#* PHP
#* Or another non-trivial open source software package that does not have a user interface and which processes data, either transforming it (e.g., compression, compiling, editing) or serving network requests.
# Obtain the software (via git or other version control system if necessary, or by downloading the appropriate archive/tarball).
# Do a build with profile generation (<code>-pg</code>) enabled -- note that both the compiler and linker will require the <code>-pg</code> option. You may need to install build dependencies.
# Decide what data you're going to use for the profiling run.# Execute your profiling plan and analyze the resultsusing <code>gprof</code>. Record appropriate information about the data processed and the execution environment.
{{Admon/tip|Share the Wealth|Make sure that each member of the group has access to the files the group was working on before the end of class (e.g., put them in a folder with world-readable permissions, post them on a public URL, or mail them to each member of the group). It would also be a good idea to share contact information within the group.}}
# Complete any of the tasks not completed by the group during the class.
# Analyze the results to find the portions of code that offer the best opportunity for optimization (these may not be the portions that consume the most time). You will probably want to look at the source code for the relevant function.
# Blog the execution environment, your results, your analysis of the results, and your experience doing this lab, including things that you learned and unanswered questions that have come up.
 
== Extra Learning ==
 
If you have interest:
* Use another profiling tool to analyze the same software.
* Blog about the results.

Navigation menu