Do we have any restrictions in SuperOffice REST-api, regarding to performance ?
I mean do we have a max concurrent request setting, any other setting in IIS , datbase etc that can be altered?
Or does the max transactions per second determines by the underlaying HardWare only.
I am doing some Load-Tests with SOAP-UI.
If just runing 20 threads(user) 1-20 thread for 2 minutes, I MAX my server out around 70-73 transactions per second.
That is quite ok.
But when doing the same test, but searching for number 2:
the transactions per second drops to around 15.
problem is that if building a FrontEnd API that calls SuperOffice API we often needs to add several calls to get a proper result back. Eg if returning a company that has External Table data (we first need to find those)
SO for my client we/they do need to send 4 Request to fetch a customer with all data , that we need for one scenario.
Search defined aproximatly as follows:
Get-external-Id-Type (Need to fetch what type of extrernal Id we have, type of Extratable entry)
Get-Contact-Id-By-External-Id (value in Extratable connected to person, ) run to get get what company to fetch
Get-Person-By-Contact-Id (fetch persons on the company)
Get-Contact-By-Id (used to fetch the company out from search of person)
In this above scenario we MAX out the server and "only gets" 4 transactions / second.
Server Spec for test-rig:
4VCpus (CPU- E5-2690 v4)
16 GB RAM
SQL-server 2016 with 16 RAM
Anyone with thoughts / tips etc on above are welcome to jump into the discussion.
Could indexes in the database on the extra-table rows help etc?
Any other things to consider to bump upp the tps-value for the scenario?