Re: IWS REST API performance questions

Jim,

In regard to your point about network bottlenecks, we were recently
measuring the performance of a predictive text-box utility that we were
implementing, where each keystroke made a new request to the server and
returned a filtered list of results. The latency was about 2-3 milliseconds
per response on a LAN, which increased to 80 milliseconds over the
Internet, which increased to 300 milliseconds when passed through an
external proxy server.

Nathan.


On Mon, May 10, 2021 at 9:55 AM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

As you might guess the best answer to all your questions is: "It
depends".....

Generally we see memory footprint and proper use on shared pools to have
the
biggest effect on this type of transaction. Rarely CPU becomes a
bottleneck
if the transactions are complicated, so I suggest you make the REST API do
as little as possible and push the bulk of the processing to asynch batch
(data queue ??)

The thing we see most often in these situations are network bottlenecks.
DNS look ups take too long, firewall rules that cause things to bounce
around, too slow of an internet connection, poorly configured line
descriptions, etc..

--
Jim Oberholtzer
Agile Technology Architects