[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ftpapi] Using http_url_post_stmf - very slow



Lorne,

There's not much information, here. "It's slow" is very hard for me to troubleshoot when it's not slow for me...

I don't think there's a "preferred approach" -- it's whatever works best for you. For sure, sending data from memory will be faster since there's no disk access involved -- but in most cases, this difference won't be noticed since network speed tends to be slower than disk speed -- but maybe it's different in your case?

-SK


On 6/8/2017 3:49 PM, Sturgeoff, Lorne wrote:

Hello list.

I have a program that uses http_url_post_stmf to send an encoded stream file to a web service (https:// etc), based on EXAMPLE7 in LIBHTTP/QRPGLESRC.

When we upload files to the same web service using PC tools they go in seconds. When they go with HTTPAPI using http_url_post_stmf, they go very slowly indeed. I have the job running at priority 19 and the system is not burdened at all (Power 7 running IBM i 7.2).

Is this the preferred approach to send stream files to a web service or should I be using a different api?

Thanks,

Lorne.



--
_______________________________________________
Ftpapi mailing list
Ftpapi@xxxxxxxxxxxxxxxxxxxxxx
http://scottklement.com/mailman/listinfo/ftpapi