As I said in an earlier post Nathan it would be a miracle if it performed as well (given he same level of tuning) the http interface simply formats the data it receives into a call to the same stored procs that the direct calls utilize. Hard to be faster when you have an extra layer to navigate. That said - it appears from my tests to be a tiny difference.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Apr 11, 2018, at 12:34 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

On Tue, Apr 10, 2018 at 1:07 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

(The YiPs wiki suggests that the DB2 transport will be faster than the
HTTP interface using XMLSERVICE called as CGI.)


Tony Cairns, the lead developer of XMLSERVICE made that ambiguous
assertion. But he didn't support it with benchmarks.

I mentioned previously that we support customer sites that process millions
of requests for dynamic content through IBM i Apache interfaces. I can
report that the average amount of time spent in the HTTP interface is 1-2
milliseconds per request. Hopefully that puts the performance of the IBM i
Apache server into proper perspective.

It's possible that the QZDASOINIT interface is a little faster than the
HTTP interface. I don't know. But the difference would not be relevant.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.