Physikerwelt added a comment.
success criteria ---------------- I have tried to understand the graph split "experiment", but I don't understand the success criteria <https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/October_2023_scaling_update#Success_criteria>. My recommendation would be to work out the success criteria more in detail before starting the user feedback. relation to movement strategy ----------------------------- I addition I don't understand how this activity supports the Wikimedia Movement Strategy. Making it more difficult to write SPARQL queries does not seem very inclusive to me. alternatives ------------ I wonder if blazegraph (in the current configuration) is still the best solution. Coincidentally I was seeing a talk <https://annex.softwareheritage.org/public/events/2024-02-01-swhsymposium/03.VignaSebastiano.pdf> about another large graph about all software source code 34b nodes. The approach was to rewrite the software - that was written in JAVA - in rust. I imaging rewriting blazegraph in rust might give a similar (one time) performance gain as well and might make the split unnecessary. Another alternative is to translate SPARQL queries to PHP code and execute it on the mediawiki runners. Maybe some mariadb graph query extension could also be helpful. While the implementation of the sparql endpoint would be some effort, it would eliminate the effort of syncing the data from mariadb to blazegraph. TASK DETAIL https://phabricator.wikimedia.org/T356773 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Sannita, Physikerwelt Cc: Physikerwelt, EgonWillighagen, ArthurPSmith, Sj, dcausse, valerio.bozzolan, tfmorris, Gehel, Aklapper, Danny_Benjafield_WMDE, Astuthiodit_1, karapayneWMDE, Invadibot, maantietaja, ItamarWMDE, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, EBjune, KimKelting, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
