Use profiling information during compilation

[rcurtin]

Reported by rcurtin on 15 Aug 40301853 01:20 UTC
This should be a relatively simple task to set up (once the blocking bugs are resolved).

Using the testing framework set up in #18, tell the compiler to use profiling information to optimize FASTLIB.

We should see some speed gains from this.

Migrated-From: http://trac.research.cc.gatech.edu/fastlab/ticket/20

[rcurtin]

Commented by speet3 on 18 Apr 41592779 02:53 UTC
(In #94) It appears I do not have the correct permission to modify the description of the ticket, so I'll just add it as a comment for now:

The following requirements are excerpted from ticket #18 for as a reminder of intended result of this ticket:

• Build each revision of MLPACK shortly after it is checked in
• Upon encountering a build error that was not present before, alert the developer who checked in the erroneous code with a nastygram
• Be able to run unit tests on the code
• Be able to run timing tests on the code (Remove fl-build system (all the build.py files) #19)
• Be able to get profiling information for the code; CMake can compile MLPACK easily with profiling information (though I've not yet checked the code to make that change in) and then gprof can get results (Minimize preprocessor macro usage #20)
• Compare timing information and profiling information across revisions of the code
• Produce working executables for Windows, Linux, and OS X
• Provide automatically built installation packages

[rcurtin]

Commented by speet3 on 3 Dec 41674892 09:35 UTC
Just as an FYI, this is somewhat of a two-part ticket. The build server can be made to run whatever profiling tests you want, but I will need some guidance as to what that is.

[rcurtin]

Commented by rcurtin on 27 Jul 41689222 11:19 UTC
I have been investigating how to do this and I actually think it may be possible to do this entirely in CMake, with a user-specified option defining whether or not to actually perform profile-guided optimization. The process is done in three steps: compile with -fprofile-generate, run a bunch of tests to emulate standard usage, then recompile with -fprofile-use. Therefore, I'll take ownership of this ticket.

[rcurtin]

Commented by rcurtin on 8 Nov 41699463 22:40 UTC
(In #21) No more blocked by #20; let's call that it's own ticket to add profiling support, not to replace what was done here. Then, this can be resolved while that ticket is still open.

[yashsharan]

Is this issue this open?If yes ,I would like to work on this.Thanks

[rcurtin]

The issue has not been closed so it is not done. You are free to look into it.

[mlpack-bot]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions! 👍

[Shandilya21]

@rcurtin Is this issue is still open or closed? If open I would like to work on this.