From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>,
Ramsay Jones <ramsay@ramsayjones.plus.com>,
Lance Richardson <lrichard@redhat.com>,
Michael Stefaniuc <mstefani@mykolab.com>
Subject: Re: Sparse 0.5.1 RC5 released.
Date: Sun, 13 Aug 2017 14:54:00 +0100 [thread overview]
Message-ID: <CACXZuxejatWcHmdm_aczwdZBssv=R0q+vJ2dANsYT5snJLDHSA@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeR4eWwxCA0-oNfY_zBR7VGWixVuUzQr5ydvYsMFwvB1Q@mail.gmail.com>
Hi Luc,
On 13 August 2017 at 14:18, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> On 13 August 2017 at 14:10, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
>> On Sun, Aug 13, 2017 at 2:56 PM, Dibyendu Majumdar
>> <mobile@majumdar.org.uk> wrote:
>>> I am merging and testing this in my repository. I notice that after
>>> applying the changes related to killing of BBs - there is a
>>> significant slow down in Sparse.
>>>
>>> Before the merge:
>>>
>>> real: 4.3 minutes
>>> user: 4.1 minutes
>>>
>>> After the merge:
>>>
>>> real: 18.9 minutes
>>> user: 18.7 minutes
>>>
>>> I just noticed this and these are my initial tests. But I thought it
>>> worth letting you know.
>>
> Yes apologies I should have mentioned the test case:
>
> https://github.com/dibyendumajumdar/dmr_c/blob/master/tests/lcc/cq.c
>
> I am checking whether the slowdown is due to some other factor such as:
>
> a) Build options - I need to check whether my build is an optimized
> build or not.
I had optimizations switched off - but with -O2, results are not good either:
Before merge:
real: 1.6 minutes
user: 1.5 minutes
After merge:
real: 8.3 minutes
user: 8.2 minutes
I do have function based iterators so that is another thing to check.
Regards
Dibyendu
next prev parent reply other threads:[~2017-08-13 13:54 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 14:15 Sparse 0.5.1 RC5 released Christopher Li
2017-08-12 20:26 ` Michael Stefaniuc
2017-08-12 20:51 ` Luc Van Oostenryck
2017-08-12 21:36 ` Ramsay Jones
2017-08-12 21:41 ` Christopher Li
2017-08-13 12:56 ` Dibyendu Majumdar
2017-08-13 13:10 ` Luc Van Oostenryck
2017-08-13 13:18 ` Dibyendu Majumdar
2017-08-13 13:54 ` Dibyendu Majumdar [this message]
2017-08-13 14:24 ` Dibyendu Majumdar
2017-08-13 14:18 ` Luc Van Oostenryck
2017-08-13 14:25 ` Luc Van Oostenryck
2017-08-13 14:26 ` Dibyendu Majumdar
2017-08-13 15:07 ` Luc Van Oostenryck
2017-08-13 15:12 ` Dibyendu Majumdar
2017-08-13 16:40 ` Luc Van Oostenryck
2017-08-13 14:44 ` Dibyendu Majumdar
2017-08-13 15:00 ` Dibyendu Majumdar
2017-08-13 15:13 ` Luc Van Oostenryck
2017-08-13 19:03 ` Christopher Li
2017-08-13 19:10 ` Dibyendu Majumdar
2017-08-13 19:20 ` Christopher Li
2017-08-13 19:56 ` Dibyendu Majumdar
2017-08-13 20:09 ` Luc Van Oostenryck
2017-08-13 20:20 ` Dibyendu Majumdar
2017-08-13 21:16 ` Luc Van Oostenryck
2017-08-13 22:12 ` Dibyendu Majumdar
2017-08-13 22:36 ` Luc Van Oostenryck
2017-08-13 22:50 ` Dibyendu Majumdar
2017-08-13 23:03 ` Luc Van Oostenryck
2017-08-13 22:55 ` Dibyendu Majumdar
2017-08-13 23:10 ` Luc Van Oostenryck
2017-08-13 23:17 ` Dibyendu Majumdar
2017-08-13 23:20 ` Dibyendu Majumdar
2017-08-13 23:28 ` Luc Van Oostenryck
2017-08-13 23:35 ` Dibyendu Majumdar
2017-08-13 23:40 ` Luc Van Oostenryck
2017-08-13 23:44 ` Dibyendu Majumdar
2017-08-13 23:22 ` Luc Van Oostenryck
2017-08-13 23:25 ` Dibyendu Majumdar
2017-08-13 23:35 ` Luc Van Oostenryck
2017-08-13 23:42 ` Dibyendu Majumdar
2017-08-13 23:47 ` Luc Van Oostenryck
2017-08-13 23:58 ` Luc Van Oostenryck
2017-08-14 0:30 ` Luc Van Oostenryck
2017-08-14 0:30 ` Christopher Li
2017-08-14 0:34 ` Luc Van Oostenryck
2017-08-14 0:36 ` Christopher Li
2017-08-14 18:48 ` Dibyendu Majumdar
2017-08-14 18:52 ` Christopher Li
2017-08-14 18:56 ` Christopher Li
2017-08-14 18:58 ` Dibyendu Majumdar
2017-08-14 19:23 ` Christopher Li
2017-08-14 19:47 ` Christopher Li
2017-08-14 20:30 ` Christopher Li
2017-08-14 16:15 ` Luc Van Oostenryck
2017-08-14 16:17 ` Dibyendu Majumdar
2017-08-14 16:25 ` Luc Van Oostenryck
2017-08-14 16:29 ` Dibyendu Majumdar
2017-08-14 16:44 ` Luc Van Oostenryck
2017-08-14 16:54 ` Dibyendu Majumdar
2017-08-14 18:51 ` Luc Van Oostenryck
2017-08-14 18:24 ` Christopher Li
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='CACXZuxejatWcHmdm_aczwdZBssv=R0q+vJ2dANsYT5snJLDHSA@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=mstefani@mykolab.com \
--cc=ramsay@ramsayjones.plus.com \
--cc=sparse@chrisli.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: 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 NNTP newsgroup(s).