1. Andreas Synthesis
  2. PowerServer
  3. Monday, 9 September 2024 13:32 PM UTC

Hello,

We notice a lot of Latency/Ping when running our cloud client application. The issue occurs when the script calls SQL statements, such as a Select statement, followed by an update statement, for example when the user logs into the system, the User, Password is validated and then a record is inserted into the database the date and time they logged in.

Running this as a Normal/Local application takes milliseconds for the procedure to execute, but with the cloud application it can take up to 2 - 3 minutes.

Is there any settings/workarounds that can help speed up these SQL executions? For instance the IIS cache settings, Powerserver settings, etc.

We are using:

1) SQL Anywhere 17,

2) We have the "Don't Pool connection to this driver" set on the SQL Anywhere Connection Pooling, because we are using a temporary table that needs to be cleared when the client disconnects.

3) Our timeout Session is Session = 14520, Transaction 14400 and Request = 3600, MaxSpClientCache = 50.

4) We are using LongConnection in the SQLCA.dbparm, to keep the temporary table through out the connection until disconnected. 

 

Thank you,

Andreas 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 9 September 2024 15:58 PM UTC
  2. PowerServer
  3. # 1

Hi Andreas;

  IMHO, I think point #2 could be killing your overall SQL performance.

Regards ... Chris 

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Monday, 9 September 2024 16:49 PM UTC
  2. PowerServer
  3. # 2

"2 - 3 minutes"  those are crazy bad numbers.

where/how do you host?  your own server on your internal network, azure, aws?  

make sure both the database and the webapi server is on the same local network.

 

 

 

 

 

 

 

 

 

Comment
There are no comments made yet.
Ronnie Po Accepted Answer Pending Moderation
  1. Monday, 9 September 2024 21:14 PM UTC
  2. PowerServer
  3. # 3

Just a couple of ideas:

1. If you implement login validation as a stored procedure, you can combine the select and insert into one round trip to the database.

2. To implement connection pooling, if you are able to adjust all of the queries that reference your temp table, you can replace the temp table with a permanent table by adding a session id column and making it part of the primary key. You'll then delete rows as sessions expire or are logged out.

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 9 September 2024 23:58 PM UTC
Adding to what Ronnie said, use PowerServerLabels as extensively as you can: https://docs.appeon.com/ps2022r3/Grouping_server_calls.html
  1. Helpful 2
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.