Performance Metrics Sample

This article will provide metric samples for a job with 1 site and 90,000 SharePoint Items (mix of list items (20%), files (70%) and pages (10%)).

NOTE: This test was done using SharePoint Online with E2 tenant license.

Factors affecting Job Performance

Please see:

• https://qipoint.atlassian.net/wiki/x/SKQW
• https://qipoint.atlassian.net/wiki/x/OoAcAQ

Recommendations for Large Jobs

• Use recommendations in above 'Factors affecting Job Performance'
• Start with a small production site, which has less visibility (not the Company Portal home page for example), which you copy into a non-production environment to test. The 'test' sites should have a good sample of links that you would find in other sites.
• Get familiar with the Find & Replace behavior, for example, all Find & Replace URL link 'strings' are compared to links found, all link replacement strings are matched, it will not match first one and stop, it will match all and execute all Link Replacement strings against EACH URL (after they are replaced). This is in case you have 2 rules, such as replace http://oldserver and also replace /oldpath/, where one or both may execute on a single URL. Contact us if you need support for this.
• Keep a recent 'good' backup of your site before doing a find and replace.
• Break down jobs into batches. For example, if you have 1000 site collections, with 60K subsites, you should fix links in batches, the same way you may approach a large content migration job, such as 500 subsites per person per evening/weekend (or whenever you have scheduled to fix links).
• We recommend no more than 300 scheduled jobs at the same time per machine/user. More than 300 jobs at the same point in time on the same machine may have performance degradation due to conflicting XML file reads/writes (the tool queues the writes to the log files and to the job data). You can increase this number by adding more machines or users to run the jobs.
• NOTE: In our test case below, we created 300 site jobs.

Our Test Environment Used

• Microsoft Windows 7 Professional 8GB RAM, Intel Quad-Core CPU 2.6GHz
  • This machine had SharePoint Essentials Toolkit installed on it
• SharePoint Essentials Toolkit Enterprise Suite 2018 Edition v6.0.7.0
• Microsoft SharePoint Online E2 Tenant License
• Publishing Site

Test Results

The job against a single site with 90K Items/Files/Pages yielded 850,000 links (valid and broken) and took 10.5 hours using the same machine above.

Important Notes

The large number of links found (850,000) plays a large role in the time for the job to complete as some links that hang can take 1-3 seconds each to respond.

This result should not be compared to time it takes to run against multiple sites/subsites/site collections with a total of 90,000 items, as each subsite will be running in parallel of each other where this job each List ran sequentially.

The tool has a built-in caching mechanism to cache broken 'domains' so that during a job, it will not attempt to reach unreachable domains if they are part of the URL.

Find Replace

This test did not replace any URLs. To factor in Find/Replace of 20% of the links, we would factor in a 10% increase in time to complete for 4 replacement conditions.