#49318 Disable MEP plugin by default
Opened 2 years ago by mreynolds. Modified 3 months ago

Issue Description

Even if the MEP plugin is not being used/configured, it still causes a significant amount of overhead for update operations. I saw almost a 10% modrate performance boost with this plugin disabled.

It should be disable by default.

However, I'm not sure how this might impact IPA, as IPA might expect it to be enabled by default during installation.

Opening ticket for investigation...


Yes, FreeIPA does not explicitly enable mep plugin but expects it is enabled -- some of update files actually modify cn=Managed Entries,cn=plugins,cn=config content.

@abbra We have an issue where MEP causes a perf issue by default. That's why we want to disable it by default.

I would have expected that IPA does a check for the existance of the plugin rather that assuming it's there though.

@mreynolds Is there a reason we couldn't track down the perf issue instead? Perhaps if there are no mep configs we shortcut and no-op?

Metadata Update from @firstyear:
- Custom field type adjusted to defect

2 years ago

@abbra We have an issue where MEP causes a perf issue by default. That's why we want to disable it by default.
I would have expected that IPA does a check for the existance of the plugin rather that assuming it's there though.
@mreynolds Is there a reason we couldn't track down the perf issue instead? Perhaps if there are no mep configs we shortcut and no-op?

It needs more investigation, but I think the perf hit is the plugin trying to see if it should do something or not. It always does an internal search for every mod.

@mreynolds Is it trying to find the mep template perhaps? Maybe we should be internally caching the template when it changes istead of looking it up each op ....

As well, we should make it postop, not pre, because there is some issue atm with it being in pre. I have some test cases commented out in lib389 that can easily break mep ;)

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.3.7.0

2 years ago

Need to file RN with doc team about this change

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.2 (was: 1.3.7.0)

3 months ago

Login to comment on this ticket.

Metadata