The following factors can directly affect the time it takes to complete the Link Scan Jobs: - Anti-virus or Offline Syncing on machine, if you have anti-virus or offline syncing on your machine that the tool is installed, this can cause significant performance issues with the tool. Please see our User Manual on the Exclusion rules to set up in the Antivirus program. http://www.qipoint.com/user_manuals
- Network speed (between machine running tool and SharePoint Web Server(s))
- Number of links in the files and pages
- Number of broken links in the files and pages (the tool does not just 'ping' the URL target but it waits to try to resolve the website, sometimes a website can take time to respond, you may adjust the timeout setting in the Links→Options page).
- Number of SharePoint items and files to parse
- If you are parsing within File Contents such as within MS Office or PDF files
- File size exclusion (we have default of 20MB limit on file size in the Options page), this can be increased but will affect the time to complete if you have large files
- Find/Replace - how many replacement conditions & how many replacement links needed
TIPS - When you are only fixing links, change the timeout setting to 25000ms (25 seconds) under Links->Manage→Options to reduce time the application waits for server responses for unresponsive links
- Keep the Find/Replace rules to under 50 per Job
- Split Large Lists (greater than 5000) into separate jobs so they can be run in parallel
- Have separate machines to run the jobs in parallel and in batches of 300 sites/jobs at one time
- SharePoint Online (Office 365): Users can potentially have slower connections, and Office 365 throttling can also cause further bottlenecks. If possible, use an Azure Virtual Machine to run jobs as it will be closer to the Office 365/SharePoint Online farm than your on-premises network. If getting throttling errors such as 429 errors, be sure to turn ON the 'Apply SPO Throttling prevention' option in Home→Settings of the SharePoint Essentials Toolkit (v6.3.0.0 and higher).
PDF files have had issues with our tool in some cases. It is due to the types of PDFs, how they were created, and location of links in the PDFs that cause our tool to incorrectly manage memory/buffer and therefore if you find a site taking a very large amount of data, try removing it (file extension) from the job to run separately later. We are working on a fix for this but for now, if you encounter this issue of large memory used by only certain sites, try removing the PDF extension from the File Contents extensions section of the Job Options page.
information is also included in the Documentation (with screenshots) included with your download. If you need further assistance, please feel free to contact us! |