JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Apoorv Gangwar — Thu, 14 Jun 2018 03:09:17 GMT

The problem is this amount of data will flow every 5 minutes from mulesoft.
I had a discussion with Appian support and according to them, doing huge data transactions through web API not recommended. They suggested that mulesoft should directly connect to Appian DB and send the data.

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Justin Watts — Wed, 13 Jun 2018 12:31:33 GMT

Agree with Alok. Mulesoft is a flexible middleware. I expect a workflow could be developed that would allow for batched calls to Appian.

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

aloks0189 — Wed, 13 Jun 2018 08:40:04 GMT

Are there any possibility, where we can ask the mulesoft to send the data in batch. Because holding so huge amount of data in memory and performing your operation over this is never recommended as this will cause performance issues.

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Apoorv Gangwar — Wed, 13 Jun 2018 06:13:29 GMT

100 MB of data is in JSON format, which mulesoft sends through Web API. Then we save this data into db.

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Apoorv Gangwar — Wed, 13 Jun 2018 06:10:28 GMT

Web API is simply inserting the relevant data out of 100 MB data to DB by starting a process model which in turn triggers a process model. Batching of data is not possible.

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

aloks0189 — Tue, 12 Jun 2018 22:09:29 GMT

Hi Apoorv Gangwar what do you mean by 100 mb of data? Is that a file such as excel , CSV contains plenty of rows or a file like a document.

Because if it's the excel or CSV which contains the data retrieved from db, then I believe you should process the in batch size instead of processing the whole amount of data.

But if it's a binary data, then may I know, how are you transferring the document to the client?

RE: JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Justin Watts — Tue, 12 Jun 2018 21:55:19 GMT

What is the Web API doing functionally speaking? That's a large amount of data to send to the endpoint at once, and depending on the activities you are executing (e.g. starting processes, calling costly functions), it seems just to be an expensive operation. I would first consider batching the data into smaller chunks if possible, as well as analyzing the Web API to see if it can be optimized at all.