From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,3a6a9f1d654285ba X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!news.glorb.com!news2.glorb.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!news.skynet.be!195.238.0.222.MISMATCH!newsspl501.isp.belgacom.be!tjb!not-for-mail Date: Fri, 04 Sep 2009 15:50:06 +0200 From: Olivier Scalbert User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada Shootout program for K-Nucleotide (patches) References: <4a743343$0$32674$9b4e6d93@newsspool2.arcor-online.net> <3f9f9e21-e088-4fbe-baac-dd43fdf6b911@r38g2000yqn.googlegroups.com> <4a757b0d$0$31328$9b4e6d93@newsspool4.arcor-online.net> <4a9fc85a$0$2850$ba620e4c@news.skynet.be> <1a5e1270-6a0a-4fff-a9b4-965abe610b69@o9g2000yqj.googlegroups.com> <4a9fdd46$0$2853$ba620e4c@news.skynet.be> <4aa0afbf$0$2864$ba620e4c@news.skynet.be> <3df8815d-b65a-4f73-9015-65375dcff113@x38g2000yqb.googlegroups.com> <4aa0e963$0$2868$ba620e4c@news.skynet.be> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4aa11b28$0$2864$ba620e4c@news.skynet.be> Organization: -= Belgacom Usenet Service =- NNTP-Posting-Host: b490edc1.news.skynet.be X-Trace: 1252072232 news.skynet.be 2864 81.246.238.10:38119 X-Complaints-To: usenet-abuse@skynet.be Xref: g2news2.google.com comp.lang.ada:8153 Date: 2009-09-04T15:50:06+02:00 List-Id: Ludovic Brenta wrote: > On Sep 4, 12:17 pm, Olivier Scalbert > wrote: >> Mmmm, 3 blocks are still reachable. 3 workers ? > > Yes, these are the task control blocks. Perhaps there is a way to > teach valgrind to ignore those as normal. > >> Second, let's profile: >> $ valgrind --max-stackframe=20000000 --leak-check=yes >> ./knucleotide.gnat_run < fasta/fasta25m.dat >> >> 25 minutes later ... >> callgrind_annotate --inclusive=yes --tree=both --auto=yes >> callgrind.out.14048 > callgrind_out_14048.txt > > OK, now try "kcachegrind callgrind.out.14048" and you can navigate > graphically in the call graph and see where the time is spent. > > -- > Ludovic Brenta. What an impressive program ! Should I rerun with --dump-instr=yes and --trace-jump=yes ? (I run it on a 32 bits linux) Olivier