Custom client side to send rpc request batch update

Engines Form Engine
, ,
1

Hi,

In our team we have use case in contract CDM we can upload up to 2000 vehicles and save it one time, it will take around 10 mins to be finished.
I talked to DS guys and got that solr index could make performance slow there, and in our use case we cannot ignore solr index for now because we want to search documents after finish operation.
I’m thinking about customizing FE side to send rpc request in batch for example 10 times with 200 documents for each. But I still don’t see any benefits from that if it cannot be run in parallel.
Do you think it is best practice, or it will improve perfomance if i go for client part to improve performance?

2

The following posts deal with performance problems in similiar scenarios:

https://discourse.geta12.com/t/how-to-not-block-resources-while-waiting-for-solr-commits/2493
https://discourse.geta12.com/t/how-to-improve-overall-dataservices-performance-because-of-poor-hazelcast-caching/2659/2

You might want to have a look and try to implement the changes described there.

Doing more requests in parallel won’t probably help anything because all the processing will wait for solr hard commits after every document update. You will just be blocking more servlet request processing threads by using batching in frontend.