## 4 Experimental Results
### Effect of Cooperating with Effective-Address
When there is both cooperation and _effective-address_, there is definite behavior for running threads, as can be seen in Figures 4b, 5b, 6b and 7b. Table 3 presents the efficacy of SACT with cooperation and _effective-address_ for YN problems in descending order. It can be seen that the increased efficacy of the SACT algorithm, as a function of the number of threads, occurs when the number of threads is the largest (\(H48\)). The exception to this is the YN3 problem, in which case the number of threads is also great. In YN1 and YN4, the worst efficacy is obtained with \(H40\). According to Table 4, in order to define the number of threads needed to increase the efficacy in SACT, it would be necessary to start  
Figure 6: YN3-20 \(\times\) 20. Performance of cooperation with different numbers of threads. Average of 30 tests. (**a**) Without _effective-address_. (**b**) With _effective-address_.4. with \(H32\) threads, and slowly increase the threads, being careful detect cases when SACT has a number of threads that presents a low efficacy, as in the case of YN1(\(H40\)) and YN4(\(H40\)). An interesting point related to the efficacy of the SACT algorithm is that when there is cooperation but no _effective-address_ there is no defined behavior for different threads in execution, as seen in Figures 4a, 5a, 6a and 7a. The efficacy of cooperation with the _effective-address_ procedure (Figures 4b, 5b, 6b and 7b), is noticed when, with a small number of iterations 500 SA, the value of an average makespan (MS) improves considerably when compared to the second type of cooperation (Figures 4a, 5a, 6a and 7a). For example, for YN1 with _effective-address_, the average MS is about 900 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as seen in Figure 4b. For YN1 without _effective-address_, the average MS is close to 905 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)) as shown in Figure 4a. For YN2 with _effective-address_, the average MS is close to 922 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as noted in Figure 5b. For YN2 without _effective-address_, the average MS is close to 928 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as observed in Figure 5a. Figure 7: YN4-20 \(\times\) 20. Performance of cooperation with threads. Average of 30 tests. (**a**) Without _effective-address_. (**b**) With _effective-address_ procedure. For YN3, with _effective-address_, the average MS is close to 906 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as seen in Figure 6b. For YN3 without _effective-address_, the average MS is close to 912 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as shown in Figure 6a. For YN4 with _effective-address_, the average MS is close to 922 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as noted Figure 7b. For YN4 without _effective-address_, the average MS is close to 928 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as seen in Figure 7a. It can be observed that with a Maxiter = 500, the increased efficacy is almost constant for all YN, with 6 units of improvement in makespan when _effective-address_ is used, as compared to when it is not used. When comparing the first type of cooperation (Figures 4b, 5b, 6b and 7b) and second type of cooperation (Figures 4a, 5a, 6a and 7a), when the number of iterations is 2500, the average value of MS is better for the first type of cooperation. For YN1 with _effective-address_, the average MS is approximately 896 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as seen in Figure 4b. For YN1 without _effective-address_, the average MS is approximately 898 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as shown in Figure 4a. For YN2 with _effective-address_, the average MS is approximately 904 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as noted in Figure 5b. For YN2 without _effective-address_, the average MS is approximately 905 (\(H8\), \(H16\), \(H32\), \(H40\), \(H48\)), as noted in Figure 7a. With a Maxiter = 2500, the increase in efficiency of the problem varies from 1 to 5 units of improvement in MS whether _effective-address_ is used or not used.