Re: What About Price vs. Performance?

Further tests have shown that HTML generation and display with native RPG is 
currently 30 times faster than HTML generation in the JVM.  But this is 
WebSphere 2.0, so I expect to see some improvement as I move to WAS3.0 and a 
higher release of the JVM.  There is a LOT of room for improvement in the Java 
side of things - the good news is that the JVM will simply get faster as time 
goes on, given IBM's focus.

The primary benefit of my Java approach is that I can add one record to a 
database file and change a field into a dropdown list or a checkbox rather than 
an entry field.  No programming required.  That's what I was trying to 
accomplish: allowing RPG programmers who don't know Java or HTML to be able to 
build a browser interface to their applications.  A couple more months and it 
should be ready for primetime.

Joe


---------- Original Message ----------------------------------
No, I did not not include DB I/O as I thought we were comparing
(not them apples, but) HTML versus 5250 datastream *generation*.
Presumably the DB I/O would be the same for both and should be
factored out. If I take your quotes (if don't know where they fall
on the scale from lies, damn lies, statistics, and performance
measurements):
HTML  100 msec
5250      20 msec

Then the DB I/O has to be less than 20msec, leaving at least 80
msec for the HTML generation. One could argue that the pure
DSP I/O time should be factored out as well, although
the larger volume of data for HTML might be important.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---