I tried Adivsor (latest release update 1 - VS 2008 - Intel C++ 12) on an app which has four functions which run serially and which contain for loops. When annotating on tasks I getrealistic results from parallelising. However if I annotate on the for loops instead of the functions, I get a 2X projected improvementwhich stays constant whether I run on 2 procs or 32 procs.
With for loop parallelizations I should be getting a linear increase with the # of procs.
It seems to me that Advisor is missing a for loop oriented annotation. Annotating the for loop with the TASK annotations seems to not yield a correct suitability report. Advisor seems to need more work to address for loops.
Or am I missing something ?