We're seeing an issue with managed solutions. We have an an organization which we patch many times a day with an managed solutions which represent the change. This saves time as importing our entire solution can take 1.5-2 hours.
We're now up to around 155 managed solutions on this instance. What we're seeing is a huge increase in load times. If you've looked at Fiddler when opening a record, you'll know CRM starts with main.aspx (contains the ribbon), which has an IFRAME which loads edit.aspx. It is taking ~8-9 seconds to get a response to edit.aspx from the server.
To see if this was some type of layering issue, we've built a new organization, imported the latest version of the metadata in a single solution, and imported a duplicate of the data. This new organization is on the same sever. It is taking ~1-1.5 seconds to get a response from the server now.
Can anyone comment/shed some light on this behavior? In particular, are others seeing this with importing managed solutions (I'm trying to determine if this was really the issue)? Is there a way to reverse these effects? Will importing the same solution (same Guid/unique name) cause another layer?
For the record, the system job table is cleaned regularly, and only has ~1500 records. There is some correlation to the contents of the solutions (the ones we've been incrementally building) and the increase load times. Older entities or those not often touched (for instance our stable entities from CRM 4) have a much faster load time.
- Business Goal: Provide incremental updates/fixes.
- Repro
Steps: ~155 managed solutions importing and re-importing the same entities, many dozens of times.
· Expected Results: I expect a consistent load time based on the published layer, regardless of the number of layers which it is comprised of.
· Actual Results: MUCH slower load time.
· Environment: Single box environment (CRM, SQL, e-mail is disabled). Windows 2008, SQL 2008 R2, CRM UR11v2. Not a production system.