RE: HTTPAPI Performance Issue

["Pat Kennedy (IT)" <patrken@xxxxxxx>]

Thanks for the tips.

-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, July 19, 2013 3:53 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: HTTPAPI Performance Issue

AFAIK, there's no tuning to be done in the OS or HTTPAPI...

However, there's probably places your RPG can do things faster...
-Using variable length strings instead of constantly %TRIMming -integers instead of packed/zone for counting.(very minor :) ) -how you are processing the response(XML?)..
-debug(*off)
-using CPYBYTES/MEMCOPY to copy large amounts of data instead of RPG's EVAL...
http://iprodeveloper.com/rpg-programming/breaking-64k-barrier


But it'd help to see your code.  Otherwise, best I can recommend is to use standard techniques to see where the time is being spent.

On the other hand, if your HTTPAPI using RPG is doing the work of both the JADE process and the original RPG...then it might not surprising it takes longer.  If for no other reason other than the fact that you've went from multiple threads of work being done on different boxes to a single thread.
 You could get that mutli-thread improvement back by replace the JADE process with an HTTPAPI using RPG one that writes to the original data queues and allow the original RPG to do it's thing.

I helped put together a process using HTTPAPI that send/receives XML docs bigger than 65K (we are on v5r4, so we had to use 16MB user spaces).  In fact, the reponse includes a BASE64 encoded document. That process takes
~10 seconds, including the BASE64 decode and the processing on the remote side.

Charles


On Fri, Jul 19, 2013 at 9:04 AM, Pat Kennedy (IT) <patrken@xxxxxxx> wrote:

>    Scott,
>
>
>    Are there any tuning requirements on the iSeries to use the HTTPAPI
>    API? I'm looking to replace a JADE process that consumes .NET web
>    service and have been running performance tests comparing the HTTPAPI
>    called from RPGLE versus the JADE approach. The JADE process has been
>    tuned for optimal performance and outperforms my new process using
>    HTTPAPI. I trying to justify going with this approach but have been
>    running into performance issues.
>
>
>    My prototype process uses HTTPAPI to consume the .NET web service
>    directly from an RPGLE program as opposed to the JADE process that uses
>    a series of data queues to communicate between RPGLE and a Java process
>    that consumes a .Net web service. My company would like to retire JADE
>    and is looking at either migrating the JADE process to WAS8 or directly
>    consuming the web service via an RPGLE program using your HTTPAPI API.
>
>
>    Your  assistance in this matter would be greatly appreciated.
>
>
>    Thank You.
>
>
>    Patrick
>
> ----------------------------------------------------------------------
> - This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> ----------------------------------------------------------------------
> -
>
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------