Can some one suggest on this please. Thanks.
Discussion posts and replies are publicly visible
I suspect that the connection pool issue is more the symptom of another issue than the root cause. There is something running wild doing all these connections and queries. This is what I would try to identify.
But, in case I repeat myself, more details result in better tips and recommendations.
We are writing into Db and whcih is causing Record sync but Appian process is writing more than 500 rows via different process intances and that is cauing connection pool drained out. Which is leading to many failed instance with large data and those must be utilizating CPU and leading to 100%. That is why asked if this understanding is correct or not.
I reiterate my earlier recommendation (from your other thread here) that you consider batching your writes differently and/or timing some of them such that you're not writing 600 separate ones all at once in different process instances.
In one of the other conversations you opened here, I said that you are just overloading the system and either need to scale down, or increase system resources. Both or one of the two options is the only thing you can do.
There is no need to discuss this any further.
Unknown said:you are just overloading the system and either need to scale down, or increase system resources.
I would argue that the answer is "proper batching" in some respect, since the issue seems to be caused by their launching of 600 simultaneous, asynchronous process instances where each instance is handling one row of an imported data file, and all those simultaneous operations is "clogging the pipe".
Batching could be the soultion but then we need to compromise on response time.