Connection Pool Issues

Any reason why you need to do 500 writes vs just 1 write (and 1 sync with multiple ids)?

It is an upload process where each row in an excel is prcessing separtely in each instance. So when an instance is writing a row into db, sync happening 

Gopu Hema said:

each row in an excel is prcessing separtely in each instance

Is there a particular reason why each row requires a separate instance to be launched for it?

each row of excel needs to be parsed and based on value it has to update few other attributes. And we process it sequentially then it is taking huge time and by doing load balancing and parallel processing, we are able to reduce the end to end process time by 10 times.

But as data is being written for the Entity having sync record defined. 

I'd suggest you could still potentially batch the processing into larger batches than 1 row each - maybe 10 rows per process instance?  This would reduce the number of sync calls considerably, and probably not increase your processing time very much overall.

An additional thing to consider would be to implement a timer at the end of each process that pauses it a few seconds.  I've set up something before where each instance gets a random number of seconds between 1 and 30, and pauses that long, which gives the back-end engines enough time to process the different instances without accidentally trying to process every single one in one big lump, and thus getting hung up on itself.

I'd suggest you could still potentially batch the processing into larger batches than 1 row each - maybe 10 rows per process instance?  This would reduce the number of sync calls considerably, and probably not increase your processing time very much overall.

An additional thing to consider would be to implement a timer at the end of each process that pauses it a few seconds.  I've set up something before where each instance gets a random number of seconds between 1 and 30, and pauses that long, which gives the back-end engines enough time to process the different instances without accidentally trying to process every single one in one big lump, and thus getting hung up on itself.

But how timer will help if process are running parallely as sync will anyways run with each write operation.

You add the delay timer prior to the Sync call (or if you're just talking about the syncing that happens automatically after a Write, then before the Write node) in each process instance.  That means instead of 500 instances all hitting write and sync within a few milliseconds of each other, they'll execute in a staggered fashion across the entire set, allowing time for the connections to open and close between the different sync calls.