Well, I just reran the query on WDQS and there are still 128 results. So it seems that the 131, the 18, and the 125 I was getting in my tests were not correct (in fact, only one out of 7 exact same queries returned a result that might have been correct, judging only from the number of results).
I tried "clear cache and hard reload" but I still got 131. Retrying once more gave me 128 again. After that it was again 131. Seems there is some randomness in this bug. I did those last few tests on Chrome, where at least performance is pretty consistent (about 10 sec on my machine). I am on Ethernet in the university.
Best regards,
Markus
On 22.12.2016 13:56, Markus Kroetzsch wrote:
On 22.12.2016 13:32, Jan Macura wrote:
Hi all,
just as for "testing".. from my quite old PC, running Firefox, connected to the Eduroam network via wi-fi, located in the Czechia, it gives:
"Brad Pitt": 128 results in 18.9s
So, Markus' 55s for the same query on better hardware, better connection, in better location (in theory), sounds quite strange.
I am on a MacBook Pro with i5 CPU and 8GB of RAM. I just retried. I just ran four times from Firefox. The results I got:
"125 results in 54.7s" (timer stopped) "18 results in 14.5s" (timer stopped) "43 results in 614.1s" (timer wouldn't stop; I cancelled this) "131 results in 37.9s" (timer stopped)
The same query seems to run faster in Chrome, where I get:
"128 results in 24.9s" "131 results in 8.1s" "131 results in 10.0s"
This part seems fairly consistent, besides the changing number of results (are there live data updates for this service that might explain this?).
Best regards,
Markus