On Sat, Dec 5, 2015 at 3:48 PM, Jim Jagielski <[email protected]> wrote:
> > > On Dec 4, 2015, at 10:25 AM, William A Rowe Jr <[email protected]> > wrote: > > > > My observation was that that the mapped pages for 2-6 fundamental > socache, lbmethod or slotmem providers are the same as for a single module > due to page alignment - load any two and you are already wasting kernel > resources and memory. > > > > Since you refer to these 3 modules, what to you recommend? That > we bundle all providers into 1 module? That's fine with me but > my point was that the whole idea of submodules and providers, > whether from us or not, was that the admin only needs to load > the ones they use. This recommendation seems to ignore this > basic advice. > That advise always applies if the module interacts with the user-agent. I just finished pointing out that only the admin causes httpd to interact with different socache, lbmethod or slotmem providers. The modules of each group combined, while appearing larger are going to occupy the same space all together in the paging schema as any one module alone. So merging the 'core' providers into a single module is a win for each admin who is using two or more mechanisms, and net-net null for any admin who consumes only one. Those who don't use the facility at all need not load even these core groups.
