The short answer is No, there is no easy way to find out why your application is slow.
Long answer:
I have never used the Equatec profiler for Silverlight, but it looks like dotTrace. In any case, both of them display the same information as xPerf .
Basically, the information you need to have in front of you says which methods and classes take the most time to execute.
If this information points to the Silverlight platform graphics engine (agcore.dll and npctrl.dll), you will need to start the slow process of determining what you did wrong.
At this point, I strongly recommend that you follow every conversation that Sima Ramchandani talked about about Silverlight's performance. In particular, PDC08 , Mix09 and Mix10 .
Step # 1 of priority optimization . Measure. Measure. To measure.
You have a clear foundation for what you are trying to improve, and set the numerical expectation when performance is enough.
This way you can verify that your changes have a positive effect on performance.
Step # 2 of primary optimization . Start deleting files.
In your case, I would start commenting out the controls outside the form. When the effect of the array improves, you find your culprit.
Step No. 3 of priority optimization . Try to fix the weak link.
How I would decide to solve this problem.
Respectfully,
- Justin Angel
source share