Sun Fire Cool Threads Oracle Configuration Notes says: Long running single threaded Oracle batch jobs may run longer on Sun Fire CoolThreads server, which is true esp. with Oracle Applications (E-Business Suite)/Payroll jobs running on Sun Fire T1000/T2000 servers.
Assuming only one thread is processing all payroll jobs on a 8 core 1.2 GHz T2000, the thread should be getting 300 million cycles per second (Here's the math: 1.2 GHz per core = 1200 MHz per core = 1200 MHz/4 threads per core = 300 MHz per thread per core). So, the performance of a single thread on this server will be something like the performance of a single thread of an US-II based server. Fortunately we have 32 such threads on 8 core T1000/T2000 servers; and it is possible to submit multiple payroll jobs by updating the value of parameter name 'THREADS' in table pay_action_parameters.
Here is how you do it from the CLI:
To retrieve the current value of 'THREADS' parameter:
To set the value for the number of payroll threads:
Experiment by increasing/decreasing the number of payroll threads until you are happy with the overall processing time with decent resource utilization.
Assuming only one thread is processing all payroll jobs on a 8 core 1.2 GHz T2000, the thread should be getting 300 million cycles per second (Here's the math: 1.2 GHz per core = 1200 MHz per core = 1200 MHz/4 threads per core = 300 MHz per thread per core). So, the performance of a single thread on this server will be something like the performance of a single thread of an US-II based server. Fortunately we have 32 such threads on 8 core T1000/T2000 servers; and it is possible to submit multiple payroll jobs by updating the value of parameter name 'THREADS' in table pay_action_parameters.
Here is how you do it from the CLI:
% sqlplus apps/apps
To retrieve the current value of 'THREADS' parameter:
SQL> select parameter_value
from pay_action_parameters
where parameter_name = 'THREADS';
To set the value for the number of payroll threads:
SQL> update pay_action_parameters
set parameter_value = <number_of_threads>
where parameter_name = 'THREADS';
SQL> commit;
Experiment by increasing/decreasing the number of payroll threads until you are happy with the overall processing time with decent resource utilization.
____________________
UltraSPARC-T1 | Cool Threads | Oracle Applications | E-Business Suite