The profile operations, such as drill-down operations and previews, in the Developer tool require additional Data Integration Service threads. To meet this requirement, you can set the Maximum Execution Pool Size parameter to a higher value than the Maximum Profile Execution Pool Size parameter. In this use case, the requirement is three times higher because the number of developers is three. A value in the range of 5 to 10 might be appropriate for the use case. If the use case varies, analyze the requirements of the developers and choose an appropriate number.

The Profiling Service Module node can run up to eight concurrent flat file profiles during peak usage. You can set the Maximum Concurrent Profile Jobs parameter to 8. This setting ensures that the analysts can run approximately one and a half profile or scorecard jobs at a time, which is more than adequate for most situations.

To improve the flat file performance, verify that the temporary directory includes at least three different directories on different physical disk drives.

If you run a profile on relational sources, you can retain the default value of 5 for the Maximum DB Connections parameter because this profile environment has multiple relational database servers. If all the profiles use one database server, the Maximum Profile Execution Pool Size parameter prevents more than 15 concurrent profile queries running at the same time. If the database servers have more than 16 cores, increase both Maximum Profile Execution Pool Size and Maximum Execution Pool Size parameters by up to 15 additional threads.