Just curious, How would you rate ArdGate's performance versus JDBCR4's?
comparing ArdGate to JDBCR4 both are using JDBC, so the performance of remote database and network should be rather close to each other.
there are some diffrences:
ArdGate is using a DB2 exit (*ARDPGM) with some overhead
ArdGate doesn't use any RPG to Java calls, it puts the data coming from DB2 to a DataQ and gets the response data back from a DataQ (1 send/receive cycle per SQL Operation)
ArdGate uses one prestarted JVM for the JDBC Work, each request is performed in a Thread of its own.
no longer needed Java Ressources are freed automatically by the garbage collector
JDBCR4 uses lots (n JNI calls for 1 SQL operation) of RPG to Java calls over JNI limiting performance
JDBCR4 uses multiple JVMs, one per Job using JDBCR4 limiting scalability of the application
The result of all this might differ for your system and requirement, but for most constellations ArdGate should be faster and scale much better. (the ODBC based solutions would be best from the performance perspective from the today available solutions, but maybe somebody is writing DRDAGate...)
The STRSQL performance for select statements via ArdGate sometimes seems to be rather slow, this is caused by DB2, pulling the complete resultset from the remote system before showing the first records.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact