|
> From: David Morris > > On our old 730, the RPG version of these applications had that > server pegged at 90% plus utilization. Throughput was poor due to the > volume of transactions. On this 825, the RPG based code only hits about > 30% CPU utilization. My testing shows that this Java workload will push > that up to about 35% CPU utilization -- more memory would increase this > number. These are unique findings, David. I'd be very interested now to see how the original RPG code was written and what it did. It's my contention that properly written RPG code will by far outperform Java code, and I find it very difficult to comprehend a database operation where Java matches RPG. One way is to use set-based updates. If you transform record-by-record processing to set processing, you will see performance improvements, but these are due to the nature of SQL, not Java. How are you doing your updates? Single record using JDBC? Set at a time SQL processing? Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
