Hi Luc, On 13 August 2017 at 14:18, Dibyendu Majumdar <mobile@xxxxxxxxxxxxxxx> wrote: > On 13 August 2017 at 14:10, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> On Sun, Aug 13, 2017 at 2:56 PM, Dibyendu Majumdar >> <mobile@xxxxxxxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
