|
Strictly from a performance point of view, you “might” get better--
performance from the HTTPAPI method, but I doubt it will make much
difference except at extremely heavy loads. Either way you need to keep
things up to date, and with the SQL option, if you run into trouble you can
call IBM. The YAJL method requires the crowd support from forums like this
one, and Scott’s attention.
I guess my take is use the tool you are most familiar with, definitely use
ILE to its full advantage, stored procedures and the like. Use the
performance tools as you are developing to set benchmarks so when you get
to full production you have some idea where things are.
Then there is the work management side of the equation, mostly memory
management. Be sure to use memory storage pools and subsystem definitions
that are built for your environment. IBM’s supplied scheme works, every
time, but it’s not as efficient in all circumstances as it could be. That’s
why they gave use tooling to manage it.
So, it’s IBM’s favorite (and correct) answer: It Depends.
Jim Oberholtzer
Agile Technology Architects
On May 3, 2023, at 12:36 AM, Mohammad Tanveer <surgum@xxxxxxxxx<mailto:surgum@xxxxxxxxx>> wrote:points.
Anyone recommend which one is better? I feel HTTPAPI is more robust and
does not kill CPU under heavy load hundred of jobs calling rest end
related questions.
Comparison
HTTPAPI / YAJL
• Easy to use, performs very well
• Full-featured, offers capabilities that none of the others do
• Requires you to download/install 3rd party software
SQL Functions in QSYS2
• Easy to use, performs very well
• Has most needed features; missing multipart; missing error details
• Included with OS, nothing to install -- but need to be up-to-date
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https://lists.midrange.com/mailman/listinfo/rpg400-l>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https://archive.midrange.com/rpg400-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l<https://lists.midrange.com/mailman/listinfo/rpg400-l>
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l<https://archive.midrange.com/rpg400-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
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.