This question is locked. New answers and comments are not allowed.
Hi,
Having a bit of anxiety attack finding out users are experiencing slow launch times on a Office plugin using Winforms.
Initially I thought is may be due to something I did, but found out it's all in the Telerik object initializations.
The delays are to the point that the solution is not shippable and I'm in a bind unless I can bring these long init times down.
Delays of 6 sec to 30 sec are being reported by many test users.
I put in some code to measure timings, which brought me to my conclusion.
I don't connect up the datasources until later, the long init times are with no data connected. Also I moved all of the ResumeLayout() and performLayout() calls to the end of the InitializeComponent() block.
Put in some more detailed timing calls, and found:
Of this excessive initialization time:
Approx 40% of the time is spent creating the Teleric controls and the BeginInits() , From <<<a>>> to <<<b>>>
Approx 60% pf the time is spent in the Teleric EndInit() calls, From <<c>> to <<<d>>>
I love the product, and chose it primarily to provide a UI that is in line with the Office suite. I've noticed other users experiencing similar issues.
Any thing else I can try?
Thanks.
Ron
Having a bit of anxiety attack finding out users are experiencing slow launch times on a Office plugin using Winforms.
Initially I thought is may be due to something I did, but found out it's all in the Telerik object initializations.
The delays are to the point that the solution is not shippable and I'm in a bind unless I can bring these long init times down.
Delays of 6 sec to 30 sec are being reported by many test users.
I put in some code to measure timings, which brought me to my conclusion.
I don't connect up the datasources until later, the long init times are with no data connected. Also I moved all of the ResumeLayout() and performLayout() calls to the end of the InitializeComponent() block.
[debug_timing] = [0s 0m] AddinModule_AddinInitialize_Start |
[0s 31m] AddinModule_AddinInitialize_End |
[0s 0m] Display Form Request - Zeroed |
[0s 0m] InitializeComponent start |
[6s 515m] InitializeComponent end |
[0s 62m] Form Loading |
[0s 0m] Lookup Data Start |
[0s 671m] Lookup Data End |
[1s 718m] Display Form |
Put in some more detailed timing calls, and found:
Of this excessive initialization time:
Approx 40% of the time is spent creating the Teleric controls and the BeginInits() , From <<<a>>> to <<<b>>>
Approx 60% pf the time is spent in the Teleric EndInit() calls, From <<c>> to <<<d>>>
private void InitializeComponent() |
{ this.SuspendLayout(); |
<<<< a >>>>> |
new Telerik.WinControls.UI....(); |
.. |
.. |
((System.ComponentModel.ISupportInitialize)....BeginInit(); |
<<<< b >>>>>> |
... |
setup properties for each forms object |
.. |
<<<<< c >>>>> |
((System.ComponentModel.ISupportInitialize)....EndInit(); |
<<<<< d >>>>> |
.. |
.. |
Moved all the ResumeLayout() and performLayout() calls here |
} |
I love the product, and chose it primarily to provide a UI that is in line with the Office suite. I've noticed other users experiencing similar issues.
Any thing else I can try?
Thanks.
Ron