I am hoping others here are having better luck than I am designing workflows for use within the vSphere web client. I am finding that the workflows I am trying to host within the web client are rendering painfully slow. The first workflow that I am attempting to make available is aimed at deploying a vm to a cluster but has a ton of information it queries the user for (all related to our configuration management rules and the way we track the assets). I've been trying to whittle things down bit by bit to see if I can find anything that gives me some big gains in the rendering time but so far I haven't hit one particular thing that gives me a big jump. At this point I have torn out all of the actions I had triggering to do things in the form that make it really functional ( I as loading up a bunch of predefined answers and quite a bit of data bindings that sort of thing). Even with the form down to the point it is really only manual entry with a few predefined answers configured from static values (no action triggering to load based on other information in the form) it is still taking 30-45 seconds from the time I click go until I can start entering data. If I launch the same form from the vCO client it loads in 3-5 seconds.
I am using an external vCO server but they are located in the same datacenter. No big latency between the two. The forms do have quite a few steps and display groups. There is also quite a bit of logic surrounding what gets displayed and what doesn't. I'm going to try stripping all of that out to see if it makes a difference.
If anyone has some general guidance in this area I'd appreciate some feedback. This is my first attempt at hosting workflows in the vSphere client and it is proving painful and nearly unusable for me so far.