Performance & Memory Impact In Relation to Assembly Count

Our current product is made up of hundreds of projects that result in hundreds of assemblies. We are investigating whether or not it makes sense to modify our build process to build these projects into just a handful of assemblies, and I'm looking for information about what the performance impact would be. Also, a significant amount of memory allocated by our application is made up of assembly images. Would this memory footprint decrease, or stay relatively the same?

Any information you can provide will be much appreciated.

Answers


After some research, it appears that merging the assemblies should not have an adverse impact on throughput performance, and that it should decrease the working set memory.

Reference:

Microsoft's Patterns & Practices Improving .NET Application Performance and Scalability Chapter 5


Need Your Help

Creating a WebService inside my MVC project

c# asp.net asp.net-mvc web-services asp.net-mvc-4

I know there's another thread about WebapiConfig.cs and RouteConfig.cs, but I can assure this is a different question.

How do I create a JGroups channel in JBoss 7.x from the configuration in the standalone.xml file?

osgi jboss7.x jgroups

I am writing an OSGI service for JBoss7.x and I need to create a new JChannel for some domain related RPC. I would like to use one of the protocol stack definitions from the standalone.xml file and...