Help! We are having a MAJOR performance problem with a new installation of production code at our company. Our new code is taking 4 times longer than in the past. What our code does is read in from a flat file, parse out the data (doing various things to it) and then update a DB/2 database. At first we thoughtit might be due to the additional I/O (database calls), but we've reduced this to a minimum by restructuring our code, and it hasn't made a difference in the performance time. Since this installation involved new fields added to the database, we've made sure our DBAs have done some re-orgs and also put some indexes in place. This did speed things up a bit, but we're still running slow enough to be in crisis. Can anyone give us some ideas of things to check? Would java memory be a factor?
The possibilities are manifold. I think you need to use a profiler to find the bottleneck(s).
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Jul 17, 2002
We were wondering what you meant by a profiler. I'm assuming you mean a type of software that can run diagnostics? Any suggestions?
A profiler will help you identify which methods take the longest time to run or are run most frequently, which is vital information for improving performance. Check out the google directory for a few options.
Joined: Jul 11, 2001
We are using JProfiler - works well.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: major slowdown with new production install