Just an update as I did some testing on concated cache timings, on a kernel that supports multiple profile loads
so for 100 iterations of profile loading I got 2.8.95 parser, profile set from cache: 0m22.961s 2.8.95 parser, profile set concated: 2m16.653s patched parser, profile set from cache: 0m15.365s patched parser, profile set concated: 0m8.108s So with out the above mentioned parser patch, I would avoid using concated caches as it results in a significant slow down With the patch doing regular caching, the load is about 33% faster. This is partly because there are fewer writes but also because some of the cache files do have multiple profiles in them (very much like the concated cache file). The concated cache with the patch isn't quite 2x as fast as regular caching. Hopefully this will help you make an informed decision as to whether this is something you want to continue doing atm. With that said, there are other benefits to multiple profiles in the same cache file that we will be taking advantage of in the future. Atomic set replacement, the ability to share dfas and other parts of the policy for better compression, etc. So better support for doing this stuff is coming. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317545 Title: AppArmor: general protection fault: 0000 [#1] SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1317545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
