From: William Cohen <wcohen@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: coverage database support
Date: Sat, 07 Jul 2007 21:55:00 -0000 [thread overview]
Message-ID: <46900BDE.2060301@redhat.com> (raw)
In-Reply-To: <468E6C00.9060405@redhat.com>
I have been working on optimizing the performance of the coverage database code.
The removed column has been removed from the table, and the type has been
changed from a string to an enums.
I also found that the collect_derivation_chain was just adding additional
elements to the vector rather than creating a new vector from scratch each time.
This was corrected reducing the runtime. A correction has been checked in CVS.
However, the killer test is testsuite/semok/twenty.stp. This creates a probe for
every possible location. For the fc6 machine I am doing the experiments on.
there about 523,000 probes. Each one of those probes would have an entry in the
table. The coverage code appears to be inserting about 450 entries per MINUTE
into the table. This would take about 38 hours to create coverage information
for this one test and generate about 2G table (which is manageable size in sqlite).
Definitely, need to improve the speed of the insertion into the table. Would
like to factor out the file names and store, have the filenames as numbers in
the main table, and have a separate table(s) store the map between number and
file name.
-Will
next prev parent reply other threads:[~2007-07-07 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 16:21 William Cohen
2007-07-07 21:55 ` William Cohen [this message]
2007-07-09 14:57 ` Unused functions and local and global variables William Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46900BDE.2060301@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).