Re: Slowness running OO on Web UI (170 Views)
Reply
Advisor
dsalkin
Posts: 30
Registered: ‎06-07-2012
Message 1 of 7 (243 Views)
Accepted Solution

Slowness running OO on Web UI

[ Edited ]

Hi Everyone,

 

A flow from my desktop  OO client takes 2 minutes. The same flow from the OO client on the  OO server also takes 2 minutes.

 

However, the same flow from the web UI - and on the OO server itself - takes nearly 5 minutes.

 

Yes, it is also running the visuals, but it's a bit too much. Can anyone help? Are there any settings which can be configured to minimise this?

 

Thanks,

 

David Salkin

HP SaaS

 

 

Please use plain text.
Valued Contributor
jadda
Posts: 94
Registered: ‎07-19-2012
Message 2 of 7 (225 Views)

Re: Slowness running OO on Web UI

Hi,

 

Can u please post  OO version u are using ? Please mention contentpack version also.

Please use plain text.
Advisor
dsalkin
Posts: 30
Registered: ‎06-07-2012
Message 3 of 7 (222 Views)

Re: Slowness running OO on Web UI

Version: 9.07.001

Content Pack: 9.0.11.10

Please use plain text.
Advisor
Peter_Sutter
Posts: 17
Registered: ‎12-18-2012
Message 4 of 7 (214 Views)

Re: Slowness running OO on Web UI

Do an "Instant Run" and see how long it takes. Instant run is like Run All, but without visuals.

Please use plain text.
Trusted Contributor
Steve_Drummond
Posts: 87
Registered: ‎10-01-2012
Message 5 of 7 (196 Views)

Re: Slowness running OO on Web UI

Even doing instant run is quite slow for us; we have taken to creating stub flows which dynamically launch the flow we want to run faster. Obviously this means the flow you launch must be capable of running headless.

Please use plain text.
Advisor
Peter_Sutter
Posts: 17
Registered: ‎12-18-2012
Message 6 of 7 (185 Views)

Re: Slowness running OO on Web UI

Good practice to break up into sub flows instead of doing everything in a single flow.

Please use plain text.
Advisor
dsalkin
Posts: 30
Registered: ‎06-07-2012
Message 7 of 7 (170 Views)

Re: Slowness running OO on Web UI

The reason for the slowness is this: that during flow execution input dialog boxes are displayed for user input above the step execution area.  But the web interface takes a very long time before it decides to display each input box.

 

However, if you keep on refreshing the step execution window while waiting for the dialog box to appear (by changing page or enabling/disabling the automatic refresh option) then the input box will appear in its proper time.

 

This defect occurs in all browser types.

 

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation