Hi Markus,
First test of your query from Paris, on a Mac Pro in my enterprise Wifi
- On Chrome:
+ First run: first results after 95s (3 results)
+ 2nd run: first results after 25s (3 results)
+ 3rd run: First results after 14s (3 results)
- On Firefox
+ First run: first results after 65s (e.g., street Q3451473)
I am waiting to see if I can get all the results....
Ghislain
El jue., 22 dic. 2016 a las 14:33, Markus Kroetzsch (<
[email protected]>) escribió:
> One last test: after understanding that many SPARQL features are a
> problem, I am trying to find simple queries. Here is a Wikidata example
> query that has no features other than triple patterns:
>
> SELECT ?street ?city ?named
> WHERE
> {
> ?street wdt:P31 wd:Q79007 .
> ?street wdt:P17 wd:Q142 .
> ?street wdt:P131 ?city .
> ?street wdt:P138 ?named .
> ?named wdt:P21 wd:Q6581072
> }
>
> ("streets named after women"; I removed labels and ORDER to make it
> simpler)
>
> The query should have 320 results by WDQS (in 1.3sec). It's taking a
> long while on my machine though. Can anyone give a runtime for this?
> Does it eventually find correct results?
>
> Markus
>
>
>
> On 22.12.2016 14:03, Markus Kroetzsch wrote:
> > 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
>
> _______________________________________________
> Wikidata mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
--
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org
_______________________________________________
Wikidata mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata
