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
7 replies
Subscribers
6 subscribers
Views
4144 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Inconsistency between time taken for write to db node to complete and the timing shown in the 'data-store-details.csv' log
chetany
A Score Level 1
over 8 years ago
Hello Everyone,
I have a query regarding the time of Write to Datastore operation reported in the log file "data_store_details.csv"
This log file breaks the total time for the write to DB query to execute in "Mean Prepare Time", "Mean Execute Time" and "Mean Transform time". Now, for one example - on one environment I am working on - the durations reported for these are 5ms, 16ms and 5ms respectively - for a total of 26ms of Mean Total time.
Now, I observed the time taken for the "Write to Datastore" node to complete in the process history of the process instance. It shows the time as 1.04 seconds. This indicates the Write to datastore node took 1.04 seconds to complete. However, from the log file - I see that the actual database operation took a total of 26ms.
So, why is there some...
OriginalPostID-265602
Discussion posts and replies are publicly visible
Parents
0
chetany
A Score Level 1
over 8 years ago
... time unaccounted for? Apparently, the Write to DB node should also have completed in around 26-30ms. But this is not the case. Similar observation was made for Write to Multiple DS node.
I think the remaining time will be needed by Appian for things like logging the DB operation(which ideally would happen in async manner), adding it in process history of the process instance, assigning to the CDT variable the output of write to DB is saved into etc.
Also, does the "Execute"/"Transform" time of a query include the network round-trip time?
Obviously, Appian has to send the DB query to the server by first opening a connection(which is managed by Hibernate internally in Appian). If the network is slow or the database latency is more, I guess we can expect to see more time lag - and hence longer duration for the DB node to complete.
Can anyone confirm if my assumption is correct? Whether this really is the case?
Please note that we are using the Orac...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
chetany
A Score Level 1
over 8 years ago
... time unaccounted for? Apparently, the Write to DB node should also have completed in around 26-30ms. But this is not the case. Similar observation was made for Write to Multiple DS node.
I think the remaining time will be needed by Appian for things like logging the DB operation(which ideally would happen in async manner), adding it in process history of the process instance, assigning to the CDT variable the output of write to DB is saved into etc.
Also, does the "Execute"/"Transform" time of a query include the network round-trip time?
Obviously, Appian has to send the DB query to the server by first opening a connection(which is managed by Hibernate internally in Appian). If the network is slow or the database latency is more, I guess we can expect to see more time lag - and hence longer duration for the DB node to complete.
Can anyone confirm if my assumption is correct? Whether this really is the case?
Please note that we are using the Orac...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data