I'm a big fan of Perl-- but a bigger fan of using the right Tool for the job.  Job design has a much bigger impact on performance than your choice of language-- so for me, the choice really centers around the environment that the jobs will run in and the expertise of the programmers that are building them.

Creating thread in Java is very easy while in Perl is very difficult. Sorting an array of strings is hard in Java as compared to Perl.

Ho sorry I don't seen your answer. I give my tOracleInput param in the other topic.

Generally speaking, Java performances are superior to Perl performances on high data volumes (and I'm responsible of Perl code generation, so I've admitted it). Perl advantages are somewhere else than performances. It doesn't mean that Perl generated code is slow, it just means that it is a slower most of the time, in particular with delimited file. The performance difference may become null or reversed when working with databases, as our benchmarks have shown.

It may also depend on the job. The best way to know it is to design your job with Perl and Java and make a performance comparison.