Is there any database parameters we need to set when using DBMS_PARALLE_EXECUTE?

Question

Hi,
I am using dbms_parallel_execute package to do some process, I call a procedure to do the some tasks and insert data using the chunks by sql. Here is my code, I am calling p_process procedure, I am using 11g 11.2.0.3.0 - 64 bit  on windows server.
DBMS_PARALLEL_EXECUTE.CREATE_TASK ('process a');
  DBMS_PARALLEL_EXECUTE.CREATE_CHUNKS_BY_SQL (
      task_name => 'process a',
     sql_stmt => 'SELECT startid, endid FROM chng_chunks',
     by_rowid => FALSE);
        dbms_parallel_execute.run_task
        ( task_name      => 'process a',
          sql_stmt       => 'begin P_process( :start_id, :end_id ); end;',
          language_flag  => DBMS_SQL.NATIVE,
         parallel_level => 24 );
This code runs very fast on a one database and I can see it uses lots of cpus but it runs very slow on a copy of the same database on another server which has more cpus and memory. I compare v$parameter vlues and those are pretty much  identical between databases. I checked the disk spaces and both servers has plenty of free space on disks.
Now my question is, is there any other parameters that we need to set/check when using dbms_parallel_execute package.
Thanks in advance.
gg

Answer 1

I don't get this. Ever. Why developers insist on comparing server1 with server2, simply because their code is running on both.
It is like comparing the athletic ability of two persons, arguing that h/w wise they are the same (i.e. human), and both have green eyes (your same software). And as because these are all the same, both persons should be able to run the 100m in the same time.
Yes, the analogy is silly.. as is the warped concept amongst many developers that server1 and server2 should exhibit the same performance when running the same code.
It. Does. Not. Work. Like. That.
Want to know why server2 is exhibiting the performance it does when running your code?
Do that by ignoring server1 as it is NOT RELEVANT.
Do that by examining the workloads and resource usage of server2, and the run and wait states of your code on server2.