• Resolved franklinliu

    (@franklinliu)


    I implemented the Watson Assistant plugin in a website. But the response speed is a bit slow. Could you please recommend some methods for improving the response speed.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi @franklinliu in wich datacenter you have the Watson Assistant service running ? Dallas, Washington ? I have the dame problem. I think move from Washington to Dallas.
    Take a look https://www.interplazahotel.com.ar

    • This reply was modified 5 years, 11 months ago by estebanp.
    Thread Starter franklinliu

    (@franklinliu)

    Thanks @estebanp. My Watson Assistant service has been implemented in Dallas.

    Thread Starter franklinliu

    (@franklinliu)

    Any more suggestions to increase the response speed?

    Plugin Author intelahelp

    (@intelahelp)

    Hello guys.

    Usually chatbot response time depends on two factors:
    1) round trip delay between user’s browser and your site hosting;
    2) round trip delay between your site hosting and IBM Watson Assistant service.

    If you can measure these two delays you can guess how to address the issue.
    If the first delay is significant, you should consult with you site hosting provider. Otherwise you, probably, should address IBM Watson Assistant support.

    Also, if it’s possible, try to allocate Watson Assistant service in the location closest to your site hosting location.

    Thread Starter franklinliu

    (@franklinliu)

    Thanks @intelahelp. I am commissioning my website. Could you please recommend some tools to measure the round trip delay between two websites?

    Plugin Author intelahelp

    (@intelahelp)

    @franklinliu,
    You can start with ping. That would give you a rough estimation (because it does not include site/servicev processing delay). Something like this would work (Mac/Linux):

    $ ping -c4 test.intelaedu.com
    PING test.intelaedu.com (94.130.133.78): 56 data bytes
    64 bytes from 94.130.133.78: icmp_seq=0 ttl=55 time=45.724 ms
    64 bytes from 94.130.133.78: icmp_seq=1 ttl=55 time=45.940 ms
    64 bytes from 94.130.133.78: icmp_seq=2 ttl=55 time=45.823 ms
    64 bytes from 94.130.133.78: icmp_seq=3 ttl=55 time=45.830 ms
    
    --- test.intelaedu.com ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 45.724/45.829/45.940/0.076 ms
    

    Next tool is curl. This tool allows to make (and debug) actual API request, but you need to call it properly. Here is an example call:

    curl -v -u "apikey:{apikey}" -X POST "https://gatewaywatsonplatform.net/assistant/api/v2/assistants/{assistant_id}/sessions?version=2018-11-08"
    

    Please refer to API documentation for the details:
    https://console.bluemix.net/apidocs/assistant-v2

    • This reply was modified 5 years, 11 months ago by intelahelp.
    • This reply was modified 5 years, 11 months ago by intelahelp.
    Ambyomoron

    (@josiah-s-carberry)

    There is a typo in the URL provided above. It should be:
    curl -v -u "apikey:{apikey}" -X POST "https://gateway.watsonplatform.net/assistant/api/v2/assistants/{assistant_id}/sessions?version=2018-11-08"
    It would be helpful to indicate here exactly how to find the apikey. The online docs are both vague and sometimes in error.

    Plugin Author intelahelp

    (@intelahelp)

    @josiah-s-carberry, thank you for your reply.
    That was an example request from the API docs. Please don’t use it as is.
    The {apikey}, URL, and {assistant_id} should be replaced with actual ones from the “API Details” section of the IBM Watson Assistant page. There is an instruction on how to get them in the plug-in settings page:
    https://imgur.com/a/1MFxWLl

    Ambyomoron

    (@josiah-s-carberry)

    Yes, of course. I merely wanted to point out that you forgot a ‘.’ between ‘gateway’ and ‘watsonplatform.net’

    I will start a separate thread regarding the other question.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Low response speed of Watson Assistant’ is closed to new replies.