Search results

Jump to: navigation, search

Page title matches

  • == Profile Probe: profile.ual == The '''profile.ual''' predefined probe profiles the execution of functions within an appli
    23 KB (3,266 words) - 03:37, 22 September 2022
  • == Heap Memory Profile Probe: hmp.ual == ...you to determine how the heap is being used in your application. The heap profile information can be used to locate "hot spots" of heap usage in your applica
    21 KB (1,708 words) - 20:28, 27 April 2021
  • == Call Path Profile Probe: callpp.ual == See also [[CallGraphProfile Predefined Probe|Call Graph Profile]].
    26 KB (2,404 words) - 01:50, 22 September 2022

Page text matches

  • == Call Graph Profile Probe: apcgp.ual == ...ns call other functions and are called by other functions. The call graph profile information can be used to locate "hot spots" within your application on wh
    12 KB (1,561 words) - 16:31, 16 July 2018
  • == Call Path Profile Probe: callpp.ual == See also [[CallGraphProfile Predefined Probe|Call Graph Profile]].
    26 KB (2,404 words) - 01:50, 22 September 2022
  • == Profile Probe: profile.ual == The '''profile.ual''' predefined probe profiles the execution of functions within an appli
    23 KB (3,266 words) - 03:37, 22 September 2022
  • == Heap Memory Profile Probe: hmp.ual == ...you to determine how the heap is being used in your application. The heap profile information can be used to locate "hot spots" of heap usage in your applica
    21 KB (1,708 words) - 20:28, 27 April 2021
  • ...ols_Reference#aprobe|aprobe]] as described under [[#Profile UAL Parameters|Profile UAL Parameters]] below. Heap tracking data will be collected for the stand
    4 KB (560 words) - 23:04, 23 October 2020
  • ...ver more memory usage. The heap can be configured to match the exact heap profile (block size and count) required by an application for maximum performance, ...ks, so fragmentation is possible, but proper analysis (using [[Heap Memory Profile Probe|hmp.ual]]) can avoid potential problems by determining program stated
    5 KB (796 words) - 14:38, 17 September 2020
  • [[Coverage_Predefined_Probe|Profile predefined probe]] [[AUG_Files_Reference#compiler_profiles file|compiler profile]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • ...appendix, we'll refer to these by their simple filename: coverage, events, profile, trace, memwatch, etc. ...te heap memory, but these may be invoked thousands of times. The coverage, profile, and trace probes are invoked for every function (and perhaps every line of
    17 KB (2,770 words) - 23:06, 27 February 2019
  • ...from prof is the call counts facility since this is adequately covered by profile.ual. See [[CallGraphProfile_Predefined_Probe|apcgp.ual]] for a probe that ...les/learn/statprof] directory has a worked example where both statprof and profile are used as appropriate.
    19 KB (2,597 words) - 19:58, 7 October 2022
  • user_function_name ::= [class_name '::' ] ''identifier'' [ profile ] profile ::= '(' [ <''type'' [ ',' ''type'' ... ]] ')'
    18 KB (2,871 words) - 14:44, 30 March 2020
  • ...ols_Reference#aprobe|aprobe]] as described under [[#Profile UAL Parameters|Profile UAL Parameters]] below. Memory operation tracking data will be collected f
    14 KB (1,510 words) - 00:37, 21 November 2020
  • : [[Profile_Predefined_Probe|Profile Probe: profile.ual]]
    8 KB (1,047 words) - 17:39, 28 February 2019
  • ...ntegrated into a number of predefined probes (coverage, memstat, memwatch, profile, statprof) and ready to use. The demand framework can be added to custom p and an example of its use is at the end of <code>$APROBE/probes/profile.apc</code>.
    8 KB (1,203 words) - 18:05, 7 February 2019
  • ...hOfTracedCalls which is still allowed but deprecated (for commonality with profile). ...active triggers. See [[Profile_Predefined_Probe#Profile_Performance_Issues|Profile Performance Issues]] for more information on this.
    22 KB (3,480 words) - 23:37, 20 March 2018
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    19 KB (2,616 words) - 17:48, 13 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    19 KB (2,646 words) - 16:58, 4 October 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    20 KB (2,666 words) - 16:55, 16 February 2022
  • ...re it is a good idea to put the appropriate command above in your <code>~/.profile</code> (for Korn or Bourne shells) or <code>~/.login file</code> (for C she
    11 KB (1,781 words) - 23:20, 17 July 2018
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    17 KB (2,324 words) - 14:00, 20 December 2018
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    18 KB (2,434 words) - 21:24, 25 October 2019
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    18 KB (2,490 words) - 01:36, 6 March 2020
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    19 KB (2,541 words) - 19:23, 1 February 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    24 KB (3,264 words) - 17:46, 13 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    25 KB (3,323 words) - 16:56, 4 October 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    25 KB (3,348 words) - 16:53, 16 February 2022
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    25 KB (3,365 words) - 17:25, 8 September 2022
  • ...used by the [[AUG_Tools_Reference#apc|apc]] compiler. The valid compiler profile names are those that appear after the PROFILENAME keyword in the <code>$APR ...elf) for the C compiler to be used by the apc compiler. The valid compiler profile names are those that appear after the PROFILENAME keyword in the file<code>
    54 KB (8,176 words) - 22:19, 26 April 2022
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    21 KB (2,789 words) - 13:58, 20 December 2018
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    22 KB (3,033 words) - 21:22, 25 October 2019
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    23 KB (3,108 words) - 01:35, 6 March 2020
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    23 KB (3,151 words) - 19:21, 1 February 2021
  • ...these are: coverage (for test coverage), memwatch (for heap memory usage), profile and statprof (for program execution time profiling), and trace (for executi
    20 KB (3,230 words) - 17:29, 22 October 2019
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    47 KB (6,597 words) - 18:56, 13 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    48 KB (6,635 words) - 17:14, 22 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    48 KB (6,656 words) - 16:55, 4 October 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    48 KB (6,681 words) - 16:52, 16 February 2022
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    48 KB (6,698 words) - 17:26, 8 September 2022
  • ==== 8.2 How can I use Aprobe's predefined probes (profile, coverage, events, memwatch, statprof) with RootCause? ==== ...o the options as well, like <code> -u profile -p -c /testdisk/probes/prog1.profile.cfg</code> .
    73 KB (12,088 words) - 21:47, 9 May 2017
  • ...d methods are resolved by explicitly specifying the parameter profile. The profile must match precisely with what has been recorded by the C compiler, so it i Each formatting subprogram is a normal C function whose parameter profile corresponds to the actual parameters on the corresponding log statement. Wh
    74 KB (11,935 words) - 00:41, 11 March 2020
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    44 KB (6,135 words) - 13:58, 20 December 2018
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    45 KB (6,325 words) - 21:21, 25 October 2019
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    46 KB (6,407 words) - 01:34, 6 March 2020
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    46 KB (6,444 words) - 01:58, 2 February 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    62 KB (8,772 words) - 17:47, 13 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    62 KB (8,792 words) - 17:02, 22 September 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    62 KB (8,800 words) - 16:57, 4 October 2021
  • (2692) create a call path profile probe (2572) add heap memory profile (hmp) probe
    63 KB (8,818 words) - 16:54, 16 February 2022
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    60 KB (8,488 words) - 13:59, 20 December 2018
  • Yes. In fact, that's the default. There is no GUI for `info'. The coverage, profile and trace probes provide a GUI to assist in building or modifying configura ...defines "ap_Profile_DoSnapshotForAll()". To call this, you would #include "profile.h" in your APC file (it's in $APROBE/include as well, which is always searc
    162 KB (25,627 words) - 17:12, 20 September 2021
  • (2572) add heap memory profile (hmp) probe (2545) add statprof option to profile address range
    61 KB (8,594 words) - 21:23, 25 October 2019

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)