Externalizing BLOBs is the nicety that can enhance the performance of SharePoint remarkably. However, dealing with TBs of content requires that tasks being performed on this large volume of data don’t hamper the performance of the SharePoint infrastructure. Consider a typical SharePoint environment where the total size of content can easily reach in TBs. An archival job from one tier of storage to another or such other BLOB transfer activity can easily choke the SharePoint servers. At peak times, if these jobs continue to run, the capacity of the SharePoint infrastructure to service the user requests is seriously compromised.
SharePoint Job throttling is the technique of regulating the performance of these tasks in any system. It can be used in situations where it is required to limit the amount of data that can be transferred in a unit of time. Long running jobs such as Migrate, Revert, Garbage Clean, BLOB Transfer, and EBS to RBS Convert etc are heavily I/O bound jobs having a potential to considerably slow down the performance of WFEs. So SharePoint job throttling is the mechanism which allows the execution of a job / task to be configured to consume system resources at various levels at different points in time. This arrangement ensures that SharePoint WFEs dedicate their maximum resources to servicing the user requests during peak hours and let these resources be consumed in completion of heavy, I/O bound jobs during the non-peak times.
StorageEdge provides comprehensive SharePoint job throttling features. When these jobs / tasks are run, various time slots can be configured to make sure that SharePoint application is not under continuous job processing stress.
Figure 1: Job Throttling Settings in StorageEdge
StorageEdge provides you the facility to configure these tasks / jobs to be run at different speeds during different timings. Different tasks such as Migrate, Revert, Garbage Clean, BLOB Transfer and EBS to RBS Convert make the use of job throttling features. This allows you to fully control the bandwidth consumption in all types of schedules. You can completely stop the bandwidth consumption in peak hours and can slow it down in normal day activity. You can increase the speed or the bandwidth consumption when it is off time or at nights and during weekends.
Hence StorageEdge ensures that WFEs continue to perform at their best when it comes to servicing the user requests at peak load hours, while managing the completion of important tasks through intelligent time-based allocation of precious resources.