Sometimes people wonder why I take so long to merge certain patches. The issue is that if some core area of the code changes, it can have a ripple effect on the rest of the system.
One of the goals of 1.4 is to improve performance. In order to demonstrate we did (and to be better able to track regressions) this meant improving our performance testing so we now have: https://wiki.yoctoproject.org/wiki/Performance_Test The QA team just produced the numbers for 1.4M6.rc1. In case its not clear, M6 is the final release milestone. The results caused them to send me an urgent email "you might want to look at the numbers". They're right, we seem to have regressed badly between M5.rc3 and M6.rc1 on multiple benchmarks. Eeek! Paul was able to track this down to a recent bitbake change: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=05d4f94c25b14ca99a1df01030edc00125f95405 Upon looking at the patch and thinking performance, it was immediately obvious to a seasoned bitbake performance hacker that the usage of keys() would cripple us. So its sad I didn't spot this on the initial review/testing. On the other hand its great that the benchmarks caused us to as the right questions and find a problem. Thankfully its easy to fix the problem as we don't need keys() here. Lets hope the rc2 benchmarks look a bit better :) Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
