RonCK - Monday, December 14, 2009 10:42 AM:
Hello everyone,
After months of fighting with horribly slow performance in out install of Aras we were able to get our IT guys to create a test server with the demo database that saw performance similar to what Peter has indicated we should see (~4-5 seconds to open a part initially, 3-4 seconds for subsequent parts). I set about migrating this database to our data step by step to see where the slow down hits. The 2 big factors seem to be the number of parameters we add (59 total, about 8 of which we could do without , and a good chunk of which, say, 30 are parametric data points that we use for scripts to auto populate other fields.) and just displaying our forms with the extra data. This form:
for instance, takes approximately 50 seconds to load initially. Once the form is cached, it can load pretty quickly. Is there any way to improve that initial load other than removing fields? Is there a way to put intermediary fields on a form that can be used to populate fields from lists without the lists being attached to properties of a part?
thanks for any more insights,
RonCK
RonCK - Tuesday, December 15, 2009 1:48 PM:
More info on this: I used 'view source' on the form to see why it might be slow. The quick loading forms in the demo database have approximately 2700 lines of html/java code. The slow loading form in the window has about 6500 lines of code. I was able to improve load times by a third by changing the field types for our lists and filter lists from drop down boxes to text boxes, but this is an unpractical solution unless there is some way to replace the functionality of the drop down box with html that only would load as needed as opposed to always loading when a form loads (even in view mode). Does anyone have any suggestions in ways to achieve this or other ways to adjust the form to improve load time? We like the granularity we currently have with parts and want to keep it if we can.
thanks,
RonCK
