Smalyshev added a comment. Running it with 16g of RAM seems to behave fine, though it takes 500% CPU (on 16 CPU machine) even when running single query. Simpler queries behave within reason, but this one for example:
prefix data: <http://www.wikidata.org/entity/> SELECT ?p WHERE { ?p (data:P31s/data:P31v)+ data:Q28640 . } This should probably become better when we have direct paths combining data:P31s/data:P31v into one, but right now this query run for 5 mins and shows no sign of stopping. Looks like unbounded traversals are not very efficient. Also, label lookups seem to be pretty expensive on top of regular query, which may be no surprise, since label is just another triple, and on top of that there's a lot of them. I wonder if having separate service to look up labels would be useful? TASK DETAIL https://phabricator.wikimedia.org/T90116 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev Cc: Beebs.systap, Haasepeter, Aklapper, Manybubbles, jkroll, Smalyshev, Wikidata-bugs, Jdouglas, aude, GWicke, daniel, JanZerebecki _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
