|
I am playing around with some sockets and I am finding that the speed at
which RPG sockets receive data is much slower than, say, a PC downloading
with a browser.
On a PC a 5mb file downloads in 3-5 seconds.
On the IBM i using GETURI or HTTPAPI the same file downloading takes around
20 seconds which is a huge difference.
These test are HTTP (not SSL). SSL I understand will slow things down more
as well, but the time difference seems to be fairly consistent.
In running debugs it seems that the servers I have tested "limit" the
amount of data on each read() from the socket to 1448 bytes (at least in
this case). This seems to be the possible bottleneck. The receiver
variable I'm using is 1mb.
I sort of understand it's up to the server to decide how much to send at
once... I am just curious if any of you that have a deeper understanding of
the OS and how these things work can explain this.
Is it simply that RPG is a "slower" language than C, etc?
Of course I'm scanning Stack Overflow for answers, but I haven't found
anything that explains this, which is why I assume it's just RPG's fault.
:)
Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
Provider!
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.