Skip to main content
poojas0006
poojas0006
March 10, 2022
Question

Write to data Store taking more time

  • March 10, 2022
  • 8 replies
  • 0 views

Hello all,

We have set up new environments and write to data store in to a table having PK and 4 columns it self takes 1.34 second which seems to be too high .

Issue we are facing with the other nodes which is inserting more data and time is at higher end which is impacting the perfomance and response time of the process.

Is there any possibilty to update some configuration or setting at server side so that write to data store takes lesser time ? Usually write to data store should not take time in seconds to just insert 4 columns .

Any pointer will be helpful .

We have on-premises env whihc is newly setup .

Thanks in advance,

Pooja

8 replies

stefanhelzle0001
stefanhelzle0001
Brainy
March 11, 2022

Is this node execution time? Be aware that the node execution time is no accurate measurement for the underlying performance. Appian is optimized to run millions of processes at the same time, not for maximum performance on a single process instance.

poojas0006
poojas0006Author
March 11, 2022

we have observed that all the unchained node is taking  more time because engine is giving priority to the chained node . All processes are slow which are not chained which log can give us more informaiton about the server or engine helath.

stefanhelzle0001
stefanhelzle0001
Brainy
March 11, 2022

Yes. This is expected behaviour. Node executions times around one second is normal and healthy.

Is this an issue for you?

gopalk2865
gopalk2865
Participating Frequently
March 14, 2022

HI Pooja, I dont think its a problem. Does your query also take lot of time when you use query entity?

stewart.burchell
stewart.burchell
July 6, 2022

The question here is: does it matter? A performance metric in isolation can be meaningless. If the process is running asynchronously from any waiting User then does it matter if it takes a few more seconds than you expected? And if it does, why does it matter? What's the impact?

christineh465186
christineh465186
July 7, 2022

agree with the comments

1. this is expected when not chained, due to prioritization -- and you should not chain just to speed it up

2. is this happening in a wizard like UX -- if not, then it should not impact the user and you can mark records 'in progress' to be hidden via default filters, locked, or tagged that in progress

but also

3. check to see what triggers or checks you have on the table within your db that could increase the time -- outside of Appian's control

Terms & ConditionsAccessibility statement