Как профилировать прогу?

Код:


declare function Main() as integer

end Main()

function Main() as integer
cls

print "Hello, world!"

sleep
function = 0
end function


Код:


@echo off
setlocal
set fbpath="%programfiles%\freebasic\"
cls

%fbpath%fbc.exe -profile prog.bas

prog.exe

%fbpath%bin\win32\gprof.exe prog.exe > profile.txt
pause
endlocal


Flat profile:

Each sample counts as 0.01 seconds.
no time accumulated

% cumulative self self total
time seconds seconds calls Ts/call Ts/call name
0.00 0.00 0.00 1 0.00 0.00 MAIN@0

% the percentage of the total running time of the
time program used by this function.

cumulative a running sum of the number of seconds accounted
seconds for by this function and those listed above it.

self the number of seconds accounted for by this
seconds function alone. This is the major sort for this
listing.

calls the number of times this function was invoked, if
this function is profiled, else blank.

self the average number of milliseconds spent in this
ms/call function per call, if this function is profiled,
else blank.

total the average number of milliseconds spent in this
ms/call function and its descendents per call, if this
function is profiled, else blank.

name the name of the function. This is the minor sort
for this listing. The index shows the location of
the function in the gprof listing. If the index is
in parenthesis it shows where it would appear in
the gprof listing if it were to be printed.

Call graph (explanation follows)


granularity: each sample hit covers 4 byte(s) no time propagated

index % time self children called name
0.00 0.00 1/1 main [193]
[3] 0.0 0.00 0.00 1 MAIN@0 [3]
-----------------------------------------------

This table describes the call tree of the program, and was sorted by
the total amount of time spent in each function and its children.

Each entry in this table consists of several lines. The line with the
index number at the left hand margin lists the current function.
The lines above it list the functions that called this function,
and the lines below it list the functions this one called.
This line lists:
index A unique number given to each element of the table.
Index numbers are sorted numerically.
The index number is printed next to every function name so
it is easier to look up where the function in the table.

% time This is the percentage of the `total' time that was spent
in this function and its children. Note that due to
different viewpoints, functions excluded by options, etc,
these numbers will NOT add up to 100%.

self This is the total amount of time spent in this function.

children This is the total amount of time propagated into this
function by its children.

called This is the number of times the function was called.
If the function called itself recursively, the number
only includes non-recursive calls, and is followed by
a `+' and the number of recursive calls.

name The name of the current function. The index number is
printed after it. If the function is a member of a
cycle, the cycle number is printed between the
function's name and the index number.


For the function's parents, the fields have the following meanings:

self This is the amount of time that was propagated directly
from the function into this parent.

children This is the amount of time that was propagated from
the function's children into this parent.

called This is the number of times this parent called the
function `/' the total number of times the function
was called. Recursive calls to the function are not
included in the number after the `/'.

name This is the name of the parent. The parent's index
number is printed after it. If the parent is a
member of a cycle, the cycle number is printed between
the name and the index number.

If the parents of the function cannot be determined, the word
`<spontaneous>' is printed in the `name' field, and all the other
fields are blank.

For the function's children, the fields have the following meanings:

self This is the amount of time that was propagated directly
from the child into the function.

children This is the amount of time that was propagated from the
child's children to the function.

called This is the number of times the function called
this child `/' the total number of times the child
was called. Recursive calls by the child are not
listed in the number after the `/'.

name This is the name of the child. The child's index
number is printed after it. If the child is a
member of a cycle, the cycle number is printed
between the name and the index number.

If there are any cycles (circles) in the call graph, there is an
entry for the cycle-as-a-whole. This entry shows who called the
cycle (as parents) and the members of the cycle (as children.)
The `+' recursive calls entry shows the number of function calls that
were internal to the cycle, and the calls entry for each member shows,
for that member, how many times it was called from other members of
the cycle.


Index by function name

[3] MAIN@0

Есть такая штука удобная - профайлинг. Когда в отдельный файлик складывается весь поименнованный список вызывов программы. И если программа вдруг критической
ошибкой обваливается, то по такому файлику можно отыскать то самое злободневное место поломки.
Освоил я это дело из чистой необходимости для своей программы Виртуального тюнинга авто, потому как прога вечно на чужих компьютерах в нужных случаях не
запускается и сложно даже дать вразумительный ответ почему.
И так я пользуюсь средой CodeBlocks, и компилятором GNU MiniGW. Там есть файлик в папке MiniGW/bin - gprof.exe, которым собственно можно производить вывод
статистики в текстовый файл. Предварительно перед компиляцией проекта следует выставить режим профайлинга. И после запускать приложение. В той же самой
директории с исполняемым файлом сгенерируется файл профайлинга gmon.out.
Теперь для вывода статистики нужно запустить из командной строки
gprof.exe (здесь указать путь приложения) > (здесь указать файл для записи статистики)

Вот и всего-то делов, а вещь на самом деле полезная!

Пару ссылок по данной теме
http://www.cs.duke.edu/~ola/courses/programming/gprof.html
http://www.lrz-muenchen.de/services/compute/linux-cluster/tuning/gprof.html
http://www.ccp4.ac.uk/dev/gprof.html