Le 22/12/2015 18:28, Luigi Assom a écrit :
I tested it from my laptop, and I found it quite slow; as example, it took:
~1.2 seconds for querying 'DNA'
~1.6 s for 'terroristi attacks'
~1.7s for 'biology technology'
For a single word query on english wikipedia this is more like 400ms for me, so I'm not sure to understand why you experienced such response times. Response times may vary depending on server load but I'm surprised you noticed more than 1 sec for simple queries like that. Did you check that you are receiving the result type/format you expect (i.e. format=json ) ? Could you re-check at different times of the day, servers may be busy around 8pm CET (time when both europe and america are active).
Your project seems to be very interesting, could you elaborate a bit more? Do you plan to use the api from a backend/automata which will need to send a lot of queries, do you have an estimation on your needs (number of queries and refresh rate)? If your process is like refreshing a set of queries regularly I'd suggest you build a daemon that send few queries (3 or 4) per minute rather than an aggressive batch with parallel processes run once a day/week/month. You should have a look at RCStream[1] which may be more appropriate to your needs (if you plan to track changes it's definitely better than refreshing the same set of queries regularly)
Thank you!