Wikidata:Requests for comment/Improving the performance of retrieving labels, descriptions and aliases
From Wikidata
Jump to navigation
Jump to search
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Not an RfC discussion --Emu (talk) 12:31, 3 February 2024 (UTC)[reply]
An editor has requested the community to provide input on "Improving the performance of retrieving labels, descriptions and aliases" via the Requests for comment (RFC) process. This is the discussion page regarding the issue.
If you have an opinion regarding this issue, feel free to comment below. Thank you! |
THIS RFC IS CLOSED. Please do NOT vote nor add comments.
Following the discussion at Wikidata:Project_chat#The_problem_with_monolinguals, it's time for a vote on the matter. The discussion had three parts: A proposal to improve performance, a suggestion to run a benchmark/study and the eventual implementation to coincide with Wikidata changing query engine/triplestore from Blazegraph to something else. Infrastruktur (talk) 20:38, 31 December 2022 (UTC)[reply]
- @Infrastruktur The linked discussion has been archived. Are you still following through with this RFC and could you describe it better here? Lectrician1 (talk) 20:08, 15 January 2023 (UTC)[reply]
- Archived discussion. I couldn't see any obvious way to make a formal suggestion without putting it through the RFC process, even if the WMDE has the final say. It will also be hard to have any meaningful conversation without benchmarks or studies. So this is more about asking the WMDE to do a benchmark, and less about whether the optimization should be implemented or not. Infrastruktur (talk) 20:46, 15 January 2023 (UTC)[reply]
- @Infrastruktur Okay, an RFC here is not going to result in any change. Technical changes should be proposed on Phabricator.
- First, it does not look like language optimization has been implemented in QLever or another graph database yet. When that has been done, well then we can use it as one of the reasons to switch to it. Second we need to actually switch to it.
- I'd recommend documenting this problem on Phabricator. Lectrician1 (talk) 01:14, 16 January 2023 (UTC)[reply]
- I agree with Lectrician. Decisions about what to do to improve performance are clearly made by WMDE. Apart from Phabricator, WMDE has communications people like Lydia with whom you can simply talk. ChristianKl ❪✉❫ 15:51, 30 January 2023 (UTC)[reply]
Info I propose to close this RfC as improper issue for RfC after 31 January 2024. Please comment if you don’t agree. --Emu (talk) 20:39, 13 January 2024 (UTC)[reply]