public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhatch at ilm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15310] _dl_sort_fini is O(n^3) causing slow exit when many dsos Date: Tue, 02 Apr 2013 13:07:00 -0000 [thread overview] Message-ID: <bug-15310-131-LenPqhdxP7@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15310-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15310 --- Comment #17 from Don Hatch <dhatch at ilm dot com> 2013-04-02 13:07:00 UTC --- (In reply to comment #16) > > > > It tests _dl_sort_init on all 17854749 graphs of up to 4 nodes in 1min8sec, > > and _dl_sort_fini on all 16777846 pairs of graphs > > (static dep graph and dynamic dep graph) of up to 3 nodes in 48sec > > How did you get these numbers? Directed graph on 4 nodes has 12 arcs. So > there only 2^{12} = 4096 directed graphs on 4 nodes. What extra data do you > need to generate? I was considering the complete graph on 4 nodes to have 16 arcs, not 12, so there are 2^16 = 65536 possible graphs (though that might be a worthwhile corner to cut... once we convince ourselves that an edge from a node to itself doesn't affect the algorithm, then yes, we could just consider 4096 of them)... and all permutations of edges lists have to be considered different, so I was taking the sum, over all 65536 graphs, of the product of the factorials of the node arities. (plus similar sums for 0,1,2,3 nodes, though they are small in comparison) > > > (on an Intel Xeon L5630 @ 2.13GHz which is a pretty fast machine I guess). > > That's probably a bit long for a confidence test run during "make check", > > so for that, I'd probably do something less, > > augmented by some randomized testing (with deterministic seed of course). > > > First optimization would be eliminate isomorphic graphs. I could assist > if I got code. I don't think we can eliminate isomorphic graphs. Whether a bug appears or not often depends on the data order. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-04-02 13:07 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-27 7:47 [Bug dynamic-link/15310] New: " dhatch at ilm dot com 2013-03-27 8:12 ` [Bug dynamic-link/15310] " dhatch at ilm dot com 2013-03-27 8:45 ` dhatch at ilm dot com 2013-03-27 12:57 ` carlos at redhat dot com 2013-03-27 14:19 ` ppluzhnikov at google dot com 2013-03-27 20:33 ` dhatch at ilm dot com 2013-03-27 20:50 ` [Bug dynamic-link/15310] New: " Ondřej Bílka 2013-03-27 20:50 ` [Bug dynamic-link/15310] " neleai at seznam dot cz 2013-03-27 21:00 ` carlos at redhat dot com 2013-03-27 21:07 ` carlos at redhat dot com 2013-03-27 21:13 ` law at redhat dot com 2013-03-27 23:44 ` dhatch at ilm dot com 2013-03-28 0:31 ` dhatch at ilm dot com 2013-03-28 7:42 ` Ondřej Bílka 2013-03-28 7:42 ` neleai at seznam dot cz 2013-03-28 10:00 ` dhatch at ilm dot com 2013-03-28 10:19 ` dhatch at ilm dot com 2013-03-28 17:09 ` law at redhat dot com 2013-03-28 17:31 ` dhatch at ilm dot com 2013-04-02 9:54 ` dhatch at ilm dot com 2013-04-02 11:31 ` Ondřej Bílka 2013-04-02 11:31 ` neleai at seznam dot cz 2013-04-02 13:07 ` dhatch at ilm dot com [this message] 2013-04-02 23:37 ` dhatch at ilm dot com 2013-04-03 7:57 ` Ondřej Bílka 2013-04-03 7:57 ` neleai at seznam dot cz 2013-04-06 21:07 ` carlos at redhat dot com 2014-06-13 13:51 ` fweimer at redhat dot com 2014-06-13 18:37 ` fweimer at redhat dot com 2021-10-27 14:58 ` adhemerval.zanella at linaro dot org 2021-10-27 14:59 ` adhemerval.zanella at linaro dot org
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=bug-15310-131-LenPqhdxP7@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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).