Hello Community, I am facing a performance issue with an API‑triggered Process Model that writes data to a MySQL database using the Write to Data Store Entity smart service . Scenario An external system invokes an Appian Web API . The API starts a Process Model . The Process Model creates a case by inserting ~25+ rows into a single database table . Inserts are done using Write to Data Store Entity (CDT‑based). The API response is sent only after the Process Model completes . Issue Total API response time is 90+ seconds . The process completes successfully and returns "Successful" , but the latency is too high for synchronous API calls. Since all records are inserted into one table , this delay seems unexpected. Current Design API → Process Model Multiple Write to Data Store Entity executions (likely one per record / loop) Inserts are mostly sequential Backend database: MySQL Questions Is it expected for Write to Data Store Entity to take this long when inserting ~25 rows into a single table ? Does Appian open a separate transaction / commit for each Write to Data Store execution? Would performance improve by: Passing all 25 records at once in a single Write to Data Store node? Using a database stored procedure for bulk inserts? In API scenarios, is it recommended to: Immediately respond to the API And continue DB inserts asynchronously in the background?

API‑triggered Process Model using Write to Data Store (MySQL) takes 90+ seconds for ~25 inserts into a single table

vishnu_appian 24 days ago

Hello Community,

I am facing a performance issue with an API‑triggered Process Model that writes data to a MySQL database using the Write to Data Store Entity smart service.

Scenario

An external system invokes an Appian Web API.
The API starts a Process Model.
The Process Model creates a case by inserting ~25+ rows into a single database table.
Inserts are done using Write to Data Store Entity (CDT‑based).
The API response is sent only after the Process Model completes.

Issue

Total API response time is 90+ seconds.
The process completes successfully and returns "Successful", but the latency is too high for synchronous API calls.
Since all records are inserted into one table, this delay seems unexpected.

Current Design

API → Process Model
Multiple Write to Data Store Entity executions (likely one per record / loop)
Inserts are mostly sequential
Backend database: MySQL

Questions

Is it expected for Write to Data Store Entity to take this long when inserting ~25 rows into a single table?
Does Appian open a separate transaction / commit for each Write to Data Store execution?
Would performance improve by:
- Passing all 25 records at once in a single Write to Data Store node?
- Using a database stored procedure for bulk inserts?
In API scenarios, is it recommended to:
- Immediately respond to the API
- And continue DB inserts asynchronously in the background?

Discussion posts and replies are publicly visible

Top Replies

alex.acosta 22 days ago +1
Certified Lead Developer

I suggest you take a look to this https://docs.appian.com/suite/help/26.3/understanding-the-health-check-report.html#slow-web-apis . As first method for improving responsiveness, make sure the a!startProcess…

Parents

0 alex.acosta
Certified Lead Developer
22 days ago

I suggest you take a look to this https://docs.appian.com/suite/help/26.3/understanding-the-health-check-report.html#slow-web-apis. As first method for improving responsiveness, make sure the a!startProcess() that is used from a Web API with isSynchronous set to false.

1. If network round-trip time to the database is high, even 25+ single-row writes can add noticeable latency, even for a single table.

2. The Write to Data Store Entity smart service writes one row at a time; bulk inserts/updates are not supported.[Write DSE]

3. If yours is a high latency network, consider using Execute Stored Procedure, as this will most likely improve performance.

4. Yes, make the DB inserts asynchronous and check the Health Check report, as this flags slow web APIs and points to which expressions/rules are taking the most time.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 alex.acosta
Certified Lead Developer
22 days ago

I suggest you take a look to this https://docs.appian.com/suite/help/26.3/understanding-the-health-check-report.html#slow-web-apis. As first method for improving responsiveness, make sure the a!startProcess() that is used from a Web API with isSynchronous set to false.

1. If network round-trip time to the database is high, even 25+ single-row writes can add noticeable latency, even for a single table.

2. The Write to Data Store Entity smart service writes one row at a time; bulk inserts/updates are not supported.[Write DSE]

3. If yours is a high latency network, consider using Execute Stored Procedure, as this will most likely improve performance.

4. Yes, make the DB inserts asynchronous and check the Health Check report, as this flags slow web APIs and points to which expressions/rules are taking the most time.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data