SharePoint 2013 and TRIM performance issue while importing documents from TRIM to SharePoint

I am looking to import documents from TRIM to SharePoint using TRIMBOCx tool. I am running into performance issue every time I upload documents from TRIM to SharePoint. However, other SharePoint site collections and sites work fine without any performance issue. I already increase the number of worker processes for SharePoint Web Application from 1 to 2. I am now working with SQL DBA to see if Audit table growth is causing such issues while importing. 

The RAM size and other infrastructure looks ok at this stage. Let me know if any one of you have any guidance on performance issue or run into similar issue.

Thanks.

Amit

August 18th, 2015 3:21am

I'm not familiar with TRIM but if you are getting decent performance transferring data to the farm from one source but not from another then it's unlikely to be resources that's holding things up.

Do a quick test; try to upload a couple of GB of files from TRIM using their tool and then try doing it by C&P from the same server that's running the migration. That'll let you see if the software is limiting you or if there's some resource (network, disk etc.) limitation that's preventing the transfer at a greater pace. With documents then generally metadata should be negligible in terms of transfer time.

Free Windows Admin Tool Kit Click here and download it now
August 18th, 2015 8:07am

Hi Alex,

We have increased the RAM and look into other hardware improvements. The issue still exists. 

The next steps I am am doing is to clear the SharePoint Config Cache in Production server to see if it helps to improve the performance. I have verified that the Audit logs are disabled so we are not making any writes to the Audit log table.

I will keep it updated.

Amit

August 19th, 2015 9:42pm

The issue got resolved after we bring in the differential document, which has been changed since last import instead of full import. It has resolved the issue now.

Amit

  • Marked as answer by Aammiitt22 2 hours 51 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2015 12:48am

The issue got resolved after we bring in the differential document, which has been changed since last import instead of full import. It has resolved the issue now.

Amit

  • Marked as answer by Aammiitt22 Monday, August 31, 2015 4:47 AM
August 31st, 2015 4:47am

Hi,

Thanks for your Sharing.

Best Regards,

Lisa Chen

Free Windows Admin Tool Kit Click here and download it now
September 6th, 2015 10:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics