Diferență între revizuiri ale paginii „PC Lab 5”

Versiunea de la data 12 aprilie 2018 16:08

Session 5

Task: run an open-source profiler (valgrind & gprof or visual studio) and improve performance of keypoint extraction in ASIFT C++ code

2. Run demo_ASIFT with the two included Adams as input images from the Sixtine Chapel. Horizontal result should look like this:

3. Modify code to only do "compute_asift_keypoints" (matching is not interesting, since it was covered in the previous session)

4. Run the valgrind profiler

eg, for cpuload program:

g++ -std=c++11 dummy.cpp -o dummy (compile program dummy)

valgrind --tool=callgrind ./dummy (run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind)

kcachegrind whateverprofile.callgrind // open profile.callgrind with kcachegrind

Note: Valgrind is also great for checking memory leaks:

valgrind --leak-check=full <path>

valgrind --tool=memcheck <path>

Points (out of 10) vs. expected performance ():

TBD

@@ Linia 14: / Linia 14: @@
 eg, for cpuload program:
-g++ -std=c++11 cpuload.cpp -o cpuload (compile program cpuload)
+g++ -std=c++11 dummy.cpp -o dummy (compile program dummy)
-valgrind --tool=callgrind ./cpuload  (run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind)
+valgrind --tool=callgrind ./dummy  (run the program with callgrind; generates a file callgrind.out.12345 that can be viewed with kcachegrind)
 kcachegrind whateverprofile.callgrind // open profile.callgrind with kcachegrind