Mandalika's scratchpad [ Work blog @Oracle | Stock Market Notes | My Music Compositions ]

Old Posts: 09.04  10.04  11.04  12.04  01.05  02.05  03.05  04.05  05.05  06.05  07.05  08.05  09.05  10.05  11.05  12.05  01.06  02.06  03.06  04.06  05.06  06.06  07.06  08.06  09.06  10.06  11.06  12.06  01.07  02.07  03.07  04.07  05.07  06.07  08.07  09.07  10.07  11.07  12.07  01.08  02.08  03.08  04.08  05.08  06.08  07.08  08.08  09.08  10.08  11.08  12.08  01.09  02.09  03.09  04.09  05.09  06.09  07.09  08.09  09.09  10.09  11.09  12.09  01.10  02.10  03.10  04.10  05.10  06.10  07.10  08.10  09.10  10.10  11.10  12.10  01.11  02.11  03.11  04.11  05.11  07.11  08.11  09.11  10.11  11.11  12.11  01.12  02.12  03.12  04.12  05.12  06.12  07.12  08.12  09.12  10.12  11.12  12.12  01.13  02.13  03.13  04.13  05.13  06.13  07.13  08.13  09.13  10.13  11.13  12.13  01.14  02.14  03.14  04.14  05.14  06.14  07.14  09.14  10.14  11.14 


Thursday, February 15, 2007
 
Speeding up Oracle Applications/Payroll processing on Niagara servers

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:
% 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.
____________________
| | |




2004-2014 

This page is powered by Blogger. Isn't yours?