How many layers deep of embedded views are you working with? If you're nesting a lot of embedded views within other embedded views, I believe there's always been a performance issue with a lot of these. I also believe @bmusson made a module that improves on the performance of embedded views (you'd have to use his components though in place of your current embedded views).
It's not so much performance as it is load times. Deeper embedded view nesting increases load times. You are also far more likely to run into issues with view params not being passed into the embedded views if youre using anything but basic value params (as opposed to array or object type params) (known bug, not sure if it's being worked on..)
Do you know if there is a solution for this? I have noticed my Rockwell VM is significantly slower than it was several years ago and I wonder if this might be the cause.
I didn't remember what I did, but if I recall I had to modify the vmx file to restrict it to using only certain cores. I think I had to look up a tool that would tell me which cores were efficiency vs performance cores. Mine were spread out and not sequential.
I disabled efficiency cores in the BIOS. Ill report back if I feel like it made a difference.
HwInfo will tell you which core is which.
On my machine, the performance cores are 0,1,10,11,12,13.
Then, I added the entries into the vmx:
processor0.use = "TRUE"
processor1.use = "TRUE"
processor2.use = "TRUE"
processor3.use = "FALSE"
processor4.use = "FALSE"
processor5.use = "FALSE"
processor6.use = "FALSE"
processor7.use = "FALSE"
processor8.use = "FALSE"
processor9.use = "FALSE"
processor10.use = "TRUE"
processor11.use = "TRUE"
processor12.use = "TRUE"
processor13.use = "TRUE"
processor14.use = "FALSE"
processor15.use = "FALSE"
Couple of other things to do is to run optimize disk (assuming you have a SSD) on your computer.
This trims the storage to free up space. That being said, if its a brand new computer, then that should not matter much. Depending on the type of VM, this can be useful as well.
The other thing to do would be to try to connect to the process using VisualVM to try to narrow down the performance issue a bit. Is the slowdown on the Designer or Gateway?
The slow down was on both designer and client. It was a new PC and i had installed it on the base machine to avoid issues with VM resourcing.
I only have single embedded views on the page as i have learn the hard way that they tend to have issues. I have gone through and reduced OPC tag bindings and opted to link directly to custom porps and then link my objects to those as some use the same tag multiple times.
I'm making a large assumption that you mean you originally were binding to entire UDT instances before?