Large performance drop with many equipment parameters

Hello,

One of the projects (Using Citect Studio 2018 R2) I am working on uses a very universal supergenie, where all configuration is done through Equipment Parameters. This makes things streamlined, and easy to automate, but we've found that there are serious performance issues.
I have attempted to raise my concerns at the size of the page dynamic objects dbf, however other members of the team who have been testing these pages are adamant that there is a distinct and significant drop in performance when there are around 1000 or more Equipment Parameters active amongst all pages / popups.
My current best guess is that it is hitting a limit in a buffer somewhere, and has to create an additional buffer / disk request that doubles the delay in response.

I have attempted to search for any knowledge on limits on Equipment Parameters, or Associations, but have not had any luck.

Besides reviewing our philosophy and redesigning these popups (something others are reluctant to do considering our time constraints), is there anything we can do
Something going on in the background? Anything we can change in the ini file to make this work better for us?
Anyone seen this behaviour before?

Hoping to get this sorted soon,

Brandon Yeats

Parents
  • One genie to rule them all. I like it, sort of. I presume you mean Equipment Runtime Parameters. Equipment characteristics should be dealt with in the model, not on the page, so good work there. Though this is the sort of thing you are risking by resolving them at runtime unfortunately. Since these are a new feature is it likely that there isn't much experience out there. Since you are using the latest version, I assume your project is in support. I suggest you get in touch with them and share your concerns.
Reply
  • One genie to rule them all. I like it, sort of. I presume you mean Equipment Runtime Parameters. Equipment characteristics should be dealt with in the model, not on the page, so good work there. Though this is the sort of thing you are risking by resolving them at runtime unfortunately. Since these are a new feature is it likely that there isn't much experience out there. Since you are using the latest version, I assume your project is in support. I suggest you get in touch with them and share your concerns.
Children
No Data