Forum Post: RE: Batch job for performing an import is taking a long time to process

  • Thread starter Thread starter romain.pennes@foederis.fr
  • Start date Start date
Status
Not open for further replies.
R

romain.pennes@foederis.fr

Guest
Hello, Our imports also take a long time to process. Especially in our main employee object which has 140 relationships and about 10 triggers. It takes about two seconds to process one record. Which means that it takes 2 hours to import 3600 records and we have an import batch job running every night on each of our customer zones. (We are using import maps with about 30 to 50 mapped fields). We tried with disabling every trigger and it actually kinda helps (With no trigger being activated, we are able to have about 3 times faster processing of imports). But still, we would like it to be way faster because we'll soon have too much customers which means the import batch jobs are getting delayed and are now running during the day (They are planned to be processed at 8pm but are so long to process that it goes almost all day long (20hours non stop of imports)). Could the "bulk" option be added to import batch jobs? Right now, it only is possible when doing manual imports but could be very useful for importing large amount of data using import batch jobs. If we aren't able to improve performance of imports, we'll soon need a second STORAGE server in our private cloud instance to divide import processing of customers into two servers, but we would like to avoid that if possible. Kind regards, Romain.

Continue reading...
 
Status
Not open for further replies.
Back
Top