This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Java file operations are heavily optimized and integrated with the OS so file IO will not be a problem.
As usual, your DB operations will be the biggest CPU time consumer.
Java Threads will let you separate the various functions - for example one input file reading Thread to ensure that records are always available for the computing Thread(s) to work on, and output writing Threads.
What is unsatisfactory about your existing PRO C program?
Joined: Aug 14, 2013
Thanks for the reply Bill...
Currently the only problem is we don't have resources who can develop in PRO*C.
This PRO*C code is being run as 16 instances and the whole instances on average take 3 hours to complete processing data from database of around 30GB.
If we migrate from PRO*C to Java, we should be able to achieve atleast this performance.
What are the important points to be taken care while doing the development in Java. As I told in my previous post, we should currently read data from files unlike reading from DB in case of PRO*c code.
Author and all-around good cowpoke
Joined: Mar 22, 2000
Important points..... hmm
Be prepared to measure / profile your Java code.
Nothing wastes more time and creates more bugs then trying to create "optimized" code rather than understandable code.
16 instances - doing intense DB work, yow! Did somebody optimize that or what?
My first step would be to write the class for reading from the input files and parsing the data only - time that on a full size file to get a good starting point. I am betting you will be pleasantly surprised.