Re: Which one of perform CPU wise.

We understand the latency issues. We just want to make sure CPU usage wont
go up when we have thousands of rest calls are made from as400 within
seconds in parallel on continuous basis during peak hours. We did notice
the CPU usage went up when we used qsystools http functions, we switched to
Scott http api to resolve this issue. Now we are asked to try new QSYS2
http functions to avoid freeware. We will try it but I noticed Scott ApI is
very light on CPU usage. It also allow us to nicely dump http logs to
troubleshoot issues. Just want to make sure we use the best apis. Is
there any known issue with Scott http functions?

On Wed, May 3, 2023 at 8:19 PM Jimmy Sansi <jsansi@xxxxxxxxx> wrote:

Will you explain more about what's going on. Because if you're trying to
get REST APIs to perform as well as local table access on the i, I think
you'll be disappointed regardless the tool you use.

On 2023-05-03 06:59, Mohammad Tanveer wrote:

Anyone using MDREST4i? Our architects are replacing as400 tables with

cloud

based tables qnd are asking us to do CRUD operations on them using REST
services. Its becoming a challenge to keep the performance as good
as possible. So performance is the key for us.

On Wed, May 3, 2023 at 6:04 PM Jim Oberholtzer <

midrangel@xxxxxxxxxxxxxxxxx>

wrote:

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> wrote:

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

points.

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
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.--

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.

--
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.