Pfps added a comment.

  Based on a quick look at various Phabricator tickets and other information it 
appears to me that the only connection between the WDQS and Wikidata edit 
throttling is that a slowness parameter for the WDQS is used to modify a 
Wikidata parameter that is supposed to be checked by bots before they make 
edits.   Further, it appears that the only reason for this connection is to 
slow down Wikidata edits so that the WDQS can keep up - the WDQS does not feed 
back into Wikidata edits, even edits by bots.  So this connection could be 
severed by a trivial change to Wikidata and the only effect would be that the 
WDQS KB might lag behind Wikidata, either temporarily or permanently, and 
queries to the WDQS might become slow or even impossible without improvements 
to the WDQS infrastructure.  I thus view it misleading to state in this 
Phabricator ticket that "performance issues [of the WDQS] cause edits on 
wikidata to be throttled", which gives the impression that the WDQS forms a 
part of the Wikidata editing process or some other essential part of Wikidata 
itself.
  
  There needs to be a very strong rationale to make breaking changes to the 
Wikidata RDFS dump.  Just improving the performance of the WDQS is not enough 
for me.

TASK DETAIL
  https://phabricator.wikimedia.org/T244341

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Pfps
Cc: Gehel, Multichill, Pfps, Mmarx, Dipsacus_fullonum, Luitzen, 
VladimirAlexiev, Lea_Lacroix_WMDE, Jheald, Daniel_Mietchen, mkroetzsch, Denny, 
Lucas_Werkmeister_WMDE, Aklapper, dcausse, CBogen, darthmon_wmde, Viztor, 
94rain, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, EBjune, merbst, 
LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Xmlizer, jkroll, 
Wikidata-bugs, Jdouglas, Snowolf, aude, Tobias1984, Manybubbles, Shizhao, 
Mbch331, Rxy
_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to