1. Kiran Patel
  2. PowerBuilder
  3. Tuesday, 8 December 2020 12:40 PM UTC

After Deploy application on client pc, I found on some pc Windows 7, Windows 10 application is very slow to retrieve data from server

Develop on Appeon PowerBuilder 2019 R2 Build 2353

Deploy on Windows 7, Windows 10 64Bit

On Development PC it take 1250 ms 

but on client pc it take 22417 ms

//My Code

Integer li_rc
String ls_string
HttpClient lnv_HttpClient
lnv_HttpClient = Create HttpClient

int ll_start, ll_used
ll_start = cpu()

// Sends request using GET method
li_rc = lnv_HttpClient.SendRequest("GET", "https://demo.appeon.com/PB/webapi_client/employee/102")
ll_used = cpu() - ll_start
// Obtains the response data
if li_rc = 1 and lnv_HttpClient.GetResponseStatusCode() = 200 then
lnv_HttpClient.GetResponseBody(ls_string)
mle_1.text = ls_string
end if
messagebox("Response Time in ms",ll_used)

 

 

i have follow this post and check the fects

https://www.appeon.com/fr/standardsupport/search/view?id=1180

https://mx80.appeon.com/standardsupport/search/view?id=1328

 

Can any one face same issue, any suggestion on this issue.

attach sample code

Thank you

Kiran Pate

 

 

Attachments (1)
Who is viewing this page
Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 9 December 2020 14:41 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Kiran;

   FWIW:  We are currently studying a phenomenon found on a few customer machines where the PB App is using the HTTPClient object. On the odd machine, the performance of the HTTP calls is noticeably slower. Interestingly enough, we found that there is a Windows 10 default network setting that "seems" to affect the HTTPClient call performance. A PowerBuilder App "can" (but not always) be much slower if  "Automatically detect settings" for Proxy setup this is enabled in network settings for the W10 O/S.

   This may or may not be your issue but if you can, testing to see if this might affect your App performance would be most appreciated. Appeon has still to be successful in replicating this issue or confirming why changing this network setting on some machines makes the difference (yet not required on most). Very strange.

Regards ... Chris

Comment
There are no comments made yet.
Kiran Patel Accepted Answer Pending Moderation
  1. Thursday, 10 December 2020 12:29 PM UTC
  2. PowerBuilder
  3. # 1

Hi Mark,

Thank you for your support, will try this also.

 

Regards... Kiran

Comment
There are no comments made yet.
Kiran Patel Accepted Answer Pending Moderation
  1. Thursday, 10 December 2020 08:46 AM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

Many thanks for your guidance. I did the steps as recommended by you and whoa! It worked in W7 :) I will also validate it in W10.

You are the torch bearer for us :) Always get great support. Many many thanks again!

 

Cheers,

Kiran

Comment
There are no comments made yet.
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 10 December 2020 03:21 AM UTC
  2. PowerBuilder
  3. # 3

Hi Kiran,

 

  1. Both Ticket 1180 and Ticket 1328 are about the performance issue of using HttpClient in PB 2017.

Since this feature has been reconstructed in PB 2019 R2, I'm not sure this issue is related to them.

 

  1. As Govinda said, avoid running over the internet and deploy an API on your LAN instead of using Appeon Demo Link (https://demo.appeon.com/PB/webapi_client/employee/102), will the issue still exist?

 

  1. It is recommended that you use other tools, like Fiddler or HTTPAnalyzer, to monitor the Headers content Settings that you capture when you send an API request in the PCs with high execution speed and with low execution speed and then compare them to see if there’s any difference. If yes, then add the corresponding SetRequestHeader method to your PB code to set the request header content and then test it again.

 

Regards,

Comment
There are no comments made yet.
Kiran Patel Accepted Answer Pending Moderation
  1. Wednesday, 9 December 2020 07:12 AM UTC
  2. PowerBuilder
  3. # 4

Thank you for reply Govinda,

In my office, I have test on 3 pc and in 2 pcs its working fine, but on one pc this issue occurred. (all 3 pc on single network)

all 3 pcs IE and Chrome browser there is no problem

On my client site test on 5 pc same on 2 pcs its working, and on 3 pcs its not working

its working fine on browser.

all pcs on same network

I think there is not latency issue, some thing in PB

On my client site and my all 3 PC, I test Appeon Powerserver Application and its working.

 

Hi Mike,

test lnv_HttpClient.SecureProtocol =   also, but same result.

Regards

Kiran Patel

Comment
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 8 December 2020 22:30 PM UTC
  2. PowerBuilder
  3. # 5

Hi Kiran,

 

Where is the API you are requesting from? Is it in the same network as the end user? or is it in the same network as the development machine? 

 

Please keep in mind that over a WAN there will always be higher latency. That is because it is now running over the internet.

 

Try calling the API directly from your browser or with the use of another tool. Try doing it from the same development machine then try from the client machine. See if there is any difference.

 

You can also try compiling your application and testing on both development machine and client machine. See the differences. This can help you determine if the latency is in the client's computer or if in fact it is a PowerBuilder problem.

 

Please do share your results here.

 

Regards,

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Tuesday, 8 December 2020 13:17 PM UTC
  2. PowerBuilder
  3. # 6

based on your posted code, you did not set the secure protocol prior to the sendrequest:

lnv_HttpClient.SecureProtocol = 


 

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