Hi while we doing load testing, we find that infragestics control rendering is taking more time, in that we find the below method is the reason for the delay
'Infragistics.Web.UI.Framework.UltraLicenseProvider.GetLicense(LicenseContext, Type, Object, Boolean)' Any way to get rid of it? I am using only trail version , but in load testing because of this page load is getting delayd? any inputs will be helpful
Its taking more than lakhs of milli sec depend upon the number of controls in the current page.
Thanks,
R.Gobinath
Hello Gobinath ,
Thank you for posting in our forum.
It appears that this issue has been previously discussed here:
http://www.infragistics.com/community/forums/t/8266.aspx
It seems that the issue was not reproducible when the page is run without a profiler.
Could you let me know how many controls you’re loading on your page and what kind of control? If you’re loading a large amount of controls or if a large amount of data is loaded in them then it’s expected for there to be a delay in the rendering of the page.
Best Regards,
Maya Kirova
Developer Support Engineer II
Infragistics, Inc.
http://www.infragistics.com/support
Hi Maya Kirova,
Thanks for your response, the controls that i am using in my page is DateTime, numeric textbox , web dialog window and mask edit controls, each 5. No grid no large data, even thought its taking time. Also if i run without profiler how can we assure that this method is not taking time.? Any workaround for this will be helpful
Hello Gobinath,
The UltraLicenseProvider class seems to be the base class for licensing (inherits from the System.ComponentModel.LicenseProvider class) and the GetLicense method implements a validation method for the license key.
Currently there’s no way to remove the calls to that method as it's essential to our licensing system.
Let me know if you have any questions.
Gobinath,
What volume of the Infragistics controls are you using? There was a fix made last year that improved performance for the licensing check and this fix is in the release of 2013 volume 1 and newer. The fix is also in the latest service release of 2012 Volume 1 and 2012 Volume 2.
Let me know if you have any questions with this matter.
his looks like a really good solution, do you mind sharing the code? I could add this for the next version of the plugin, saving some eletricity and power from thousands of servers running better optimized sites ;)