You are viewing limited content. For full access, please sign in.

Question

Question

Any way to speed up the database query activity in Workflow?

asked on August 10, 2018

I find the custom query activity to query takes between 1.5 and 4 seconds for the same activity. It seems random as to the variation and query itself takes less than 100ms when I run it in a SQL tool. Its only returning 1 to 5 rows.

This behavior is in line with pretty much every database query we have. We just setup a new set of servers on a very fast database server and I am disappointed I'm not seeing faster results.

How can I find out why its so slow? Is there a way to speed it up? Maybe cut the overhead in Workflow?

I'm specifically worried about creating a new batch sync process in WF. I'd like to make sure those activities are as fast as possible.

(Running the newest version of WF 10.2)

0 0

Replies

replied on August 13, 2018 Show version history

First question, are your databases configured in Workflow with Direct SQL connections or ODBC?

0 0
replied on August 13, 2018

Direct SQL and Oracle sources

0 0
replied on August 13, 2018

That's interesting. I've seen queries run slow periodically, but not consistently like you are describing.

How long do they take to run when you test them in the designer versus how they run in a published workflow?

Also, are you running the queries once per workflow instance, or they by any chance running in a workflow that includes looped/repeated activities?

I believe Workflow builds an xml file with the results of queries rather than keeping everything in memory, so I'd be curious to see if it is taking longer than expected to retrieve the data, or if it is taking a long time to build the data file.

0 0
replied on August 13, 2018

Is the SQL Server on the same hardware server as Laserfiche Server and Workflow?  Or is it on another Server.  

Within the same internal network?  

If it is on a different server, how many hops from one to the other?  I've seen delay times from networks.  A trace route would be able to identify where the time is most involved.

Otherwise Jason's question is the next check.

1 0
replied on August 13, 2018

@████████, different server on the same network in the same data center. I believe connected via 10G eithernet.

I don't have the access to trace route, so I'll check w/ our server admins.

@████████, by designer, do you mean just hitting the "test" button? Or clicking the "run" on the workflow? When using the "test" button on the activity the response time is generally pretty slow for the first query (1 to 2 seconds) and is faster after that (sub 1 second or so), but not super fast. 

I have run the queries in both scenarios and both are slow.

In MOST cases, I'm querying an Oracle data source.

I appreciate the interaction! Thanks!

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.