HTTPSocket CPU Utilization 2018R2 vs 2019R1.1

  1. 2 weeks ago

    Wayne G

    Jun 11 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz
    Edited 2 weeks ago

    2018R2
    -image-

    Vs 2019R1.1
    -image-

    Notice the orange line which is the utilization of the selected process.

    What's happening is multiple httpsockets access API servers. Many of the API's have rate limiting so I'm using call later with a 1000 ms delay before making the next request.

    I don't really see how I can make a 'simplified' project that will display this issue without giving access to my client's data (and that isn't going to happen)

  2. Joost R

    Jun 11 Pre-Release Testers, Xojo Pro The Netherlands

    Hmm ?

  3. Beatrix W

    Jun 12 Pre-Release Testers Europe (Germany)
    Edited 2 weeks ago

    Isn't this a known issue of the sockets in 2019r1?

    This one: Feedback Case #55709 ???

  4. Wayne G

    Jun 12 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz

    But this is a xojo.net.httpsocket not the urlconnection in that report. Maybe Xojo fixed it by making Windows behave like MacOS?

  5. Stefan A

    Jun 12 Pre-Release Testers, Xojo Pro Austria, Tirol
    Edited 2 weeks ago

    @Wayne G But this is a xojo.net.httpsocket not the urlconnection in that report. Maybe Xojo fixed it by making Windows behave like MacOS?

    In the last time we experienced that URLConnection and xojo.net.httpsocket are behaving the same.
    If one of them has issues the other one also has them.
    At the moment we're stuck at 2018r3 because of these issues (higher CPU usage, slowdowns, apps are freezing and crashing).

    Simply compare the behaviour of this sample project with 2018r3 and 2019r1.1
    https://drive.google.com/open?id=1Vao9Umi4A3-W2IskrpSjRfKRZXOaiHHZ

  6. Greg O

    Jun 12 Xojo Inc

    @Wayne G
    Are these synchronous or asynchronous?

  7. Wayne G

    Jun 13 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz

    @Greg O'Lone Are these synchronous or asynchronous?

    Don't have a choice with xojo.net.httpsockets , so asynchronous. I'm running 8 sockets in parallel with 4 being single shots (only one request made) and the others making multiple sequential requests with the 1000ms delay between requests using timer.calllater.

  8. Beatrix W

    Jun 13 Pre-Release Testers Europe (Germany)

    Have you tried CURL instead?

  9. Wayne G

    Jun 13 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz

    @Beatrix W Have you tried CURL instead?

    No and I don't believe I should need to. It works ok in 18R2, why would it not in 19R1.1?

    I have written a new super using urlconnection which I have tested ok with single requests so maybe I can make this work, but I would like to think that Xojo doesn't by choice break existing code with these updates.

  10. last week

    Wayne G

    Jun 17 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz

    I've split the project into two parts, the download data is now a console app built in 2018R2 and the GUI app is built in 2019R1.1. This adds the ability to download data using a scheduler and uses the reliable CPU cost effective version of the Xojo.Net.HTTPSocket .

  11. Derk J

    Jun 18 Pre-Release Testers, Xojo Pro

    @Wayne G how much data is being transferred?
    And what is the content type?
    How much cores does the system have and GHz (total).

  12. olivier v

    Jun 19 Pre-Release Testers, Xojo Pro Europe (France)

    @Wayne G But this is a xojo.net.httpsocket not the urlconnection in that report. Maybe Xojo fixed it by making Windows behave like MacOS?

    A similar problem seems to have been fixed with xojo/net/httpsocket: Feedback Case #55301
    Perhaps we should check with the last alpha?

    For my part, I still use version 2018 because of current httpsocket problems. I think this is the first time I've been stuck on an earlier version for so long. I hope that the Xojo team is aware that this is an important issue, httpsocket is used in many projects.

  13. 7 days ago

    Wayne G

    Jun 19 Pre-Release Testers, Xojo Pro New Zealand axisdirect.nz

    @Derk J how much data is being transferred?

    Relatively small ammounts < 1MB

    @Derk Jochems And what is the content type?

    JSON & XML

    @Derk Jochems How much cores does the system have and GHz (total).

    4 cores @ 3.5GHz, but is that relevant given Xojo only uses one core?

    @olivier v Perhaps we should check with the last alpha?

    The next one maybe.

  14. Derk J

    Jun 19 Pre-Release Testers, Xojo Pro

    @Wayne G Relatively small ammounts < 1MB
    JSON & XML
    4 cores @ 3.5GHz, but is that relevant given Xojo only uses one core?
    The next one maybe.

    I’m seeing this if i re-create the sockets (urlconn and xnet http) fast and do another request fast. Say in a button click it fast.

    It looks like somehow the socket is not destroyed instantly. Maybe because it keeps waiting for the request to timeout (exception) before they are actually destroyed?

or Sign Up to reply!