Performance Implications of AdaptingExportProvider

Jun 26, 2009 at 4:01 PM
Edited Jun 26, 2009 at 4:02 PM

Hi,

The root of the export provider topology inside of CompositionContainer is an AdaptingExportProvider. This is needed to provide the contract adapter feature.

Most applications (wild guess >80%) will not need contract adapters, but when using CompositionContainer they will still incur the cost of AdaptingExportProvider's search for contracts with CompositionConstants.AdapterContractName, and currently there is no way for applications to  turn this off.

For large applications which are not using contract adapters, is the performance implications of AdaptingExportProvider serious, or since we are dealing with many components is the additonal overhead minor? Has anyone run tests around this on a real app?

Regards,

Eamon O'Tuathail

http://www.clipcode.com

 

 

Jun 26, 2009 at 4:21 PM

Hi Eamon,

This will no longer be the case in the next release.

Thanks for the feedback.

Nick

From: Eamon_OTuathail [mailto:notifications@codeplex.com]
Sent: Friday, June 26, 2009 9:01 AM
To: Nicholas Blumhardt
Subject: Performance Implications of AdaptingExportProvider [MEF:60786]

From: Eamon_OTuathail

Hi,

The root of the export provider topology inside of CompositionContainer is an AdaptingExportProvider. This is needed to provide the contract adapter feature.

Most applications (wild guess >80%) will not need contract adapters, but when using CompositionContainer they will still incur the cost of AdaptingExportProvider's search for contracts with CompositionConstants.AdapterContractName, and currently there is no way for applications to turn this off.

For large applications which are not using contract adapters, is the performance implications of AdaptingExportProvider serious, or since we are dealing with many components is the additonal overhead minor? Has anyone run tests around this on a real app?

Regards,

Eamon O'Tuathail

http://www.clipcode.com

Read the full discussion online.

To add a post to this discussion, reply to this email (MEF@discussions.codeplex.com)

To start a new discussion for this project, email MEF@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com