Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
8 subscribers
Views
1134 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi, A question related to Appian Performance, we are trying to analy
pingc
over 8 years ago
Hi,
A question related to Appian Performance, we are trying to analyzing how web service call load impacting our performance in production, one thing we have noticed is for shared process model which includes the web service call node, the duration of the process execution for UI chained is much faster than it was called by the back-end parent process model, which means not in the activity chain, is it what Appian behaves normally? UI chained process model call takes priority?
If anyone could help clarify this, that would be quite helpful.
Thanks,
Ping
OriginalPostID-198252
OriginalPostID-198252
Discussion posts and replies are publicly visible
0
Tejas Kargutkar
Appian Employee
over 8 years ago
Appian works using both foreground and background operations.
When activity chaining is enabled, the nodes are executed in the foreground, take precedence, whereas unattended nodes that are not chained are executed in the background. When a node is executed in the foreground, it will execute with a higher priority over the nodes executed in the background, thus completing faster. Attended nodes, chained or not, are always executed in the foreground.
However this should not be used as a solution to execute nodes faster. We need to find out where the bottleneck is and make the process run fast without unwanted activity chaining.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pingc
over 8 years ago
Thanks Ejas to clarify this! The reason why I am asking is in production we have background workflow process which initiated from web and foreground process which is initiated from CSR, at one point we got complaint from CSR UI is slow, then we begin to analyze the bottleneck and one of the web service call subprocess (getAccount) is used for both channel, after analyzing the duration for completing this subprocess, there are two tiers noticed, one is much faster(i.e. 0.5s) which has the activity chaining enabled, but the other one is slower(2s) which doesn't have chaining enabled. So as per your explanation, that makes sense to me.
Thanks,
Ping
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel