|
Joe, To add a little spice to the mix, I tried a similar test. I Loaded the HTTP server, and 2 RPG application servers. Then accessed my Chart of Accounts maintenance program at http://209.150.202.196/glcamt/begin.isp, then clicked the PgUp Link 210 times. The before and after WRKACTJOB screen shots follow: Subsystem/Job Type Pool Pty CPU Int Rsp AuxIO CPU % QHTTPSVR SBS 2 0 .2 0 .0 RDWEBSHR BCH 2 25 15.1 0 .4 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEB SBS 2 0 .3 0 .0 GLCAMT BCH 2 20 .9 0 .0 GLJOEN BCH 2 20 .8 0 .0 Subsystem/Job Type Pool Pty CPU Int Rsp AuxIO CPU % QHTTPSVR SBS 2 0 .2 0 .0 RDWEBSHR BCH 2 25 25.2 0 .4 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEBSHR BCI 2 25 .5 0 .0 RDWEB SBS 2 0 .3 0 .0 GLCAMT BCH 2 20 20.3 0 .0 GLJOEN BCH 2 20 .8 0 .0 I mentioned earlier that I use an HTTP server plug-in (message server) to route requests to the RPG application server (GLCAMT). The downloaded HTML is 5.8K per page, which is 76% larger than your 3.3K page. My HTTP Server used only 10 seconds which is half of yours. But my RPG program use nearly 20 seconds which is more than double that of yours. The larger page size would account for some of the difference, but not all. I'm wondering whether I need to fine-tune the API used by the RPG program? Also, I'm using a 170-2290 with 320 meg RAM with a CPW rating of apx. 70. What's your machine? And Brad, what's your machine? Nathan. +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
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.