Lines Matching full:cycles
171 has a significant fraction of its cost in <emphasis>cycles</emphasis> (sets
378 <sect2 id="cl-manual.cycles" xreflabel="Avoiding cycles">
379 <title>Avoiding cycles</title>
392 <para>Recursion is quite usual in programs, and therefore, cycles
395 about cycles which makes you want to avoid them? And: How can
396 cycles be avoided without changing program code?</para>
398 <para>Cycles are not bad in itself, but tend to make performance
403 cycles, this does not hold true: callees of a function in a cycle include
406 of cycles. Further, all functions in a cycle are collapsed into artifical
409 <para>Now, when a program exposes really big cycles (as is
418 <para>Despite the meaningless of inclusive costs in cycles, the big
421 misguiding visualization. However, often cycles appear because of
425 cycles. In such cases, incorrect handling of cycles by not detecting
432 <para>After describing why cycles are bad for profiling, it is worth
439 quite capable of avoiding cycles, it has to be used carefully to not cause
443 <para>A further possibility to avoid cycles in Callgrind's profile data
449 possibly breaking cycles, this is used in Callgrind to skip
806 Also see <xref linkend="cl-manual.cycles"/>.</para>
828 call chain. See <xref linkend="cl-manual.cycles"/>.</para>
838 See <xref linkend="cl-manual.cycles"/>.</para>
848 See <xref linkend="cl-manual.cycles"/>.</para>
858 See <xref linkend="cl-manual.cycles"/>.</para>
