On Jun 17, 2019, at 03:41 PM, Finn Aarup Nielsen <faan(a)dtu.dk> wrote:
Changing the subject a bit:
Well... Changing the subject a *lot*, to an extent probably
worthy of its own subject line, and an entirely new thread,
not only because it seems more relevant to the "shex-simple
Toolforge tool" you reference, than to anything in this thread
about scaling the back-end.
Ted
I am surprised to see how many SPARQL requests go to
the endpoint when performing a ShEx validation with the shex-simple Toolforge tool. They
are all very simple and quickly complete. For each Wikidata item tested, one of our tests
[1] requests tens of times. That is, testing 100 Wikidata items may yield thousands of
requests to the endpoint in rapid succession.
I suppose that given the simple SPARQL queries, these kinds of requests might not load
WDQS very much.
[1]
https://tools.wmflabs.org/shex-simple/wikidata/packages/shex-webapp/doc/she…
--
A: Yes.
http://www.idallen.com/topposting.html
| Q: Are you sure?
| | A: Because it reverses the logical flow of conversation.
| | | Q: Why is top posting frowned upon?
Ted Thibodeau, Jr. // voice +1-781-273-0900 x32
Senior Support & Evangelism // mailto:tthibodeau@openlinksw.com
//
http://twitter.com/TallTed
OpenLink Software, Inc. //
http://www.openlinksw.com/
20 Burlington Mall Road, Suite 322, Burlington MA 01803
Weblog --
http://www.openlinksw.com/blogs/
Community --
https://community.openlinksw.com/
LinkedIn --
http://www.linkedin.com/company/openlink-software/
Twitter --
http://twitter.com/OpenLink
Facebook --
http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers