Reinhard_Mueller added a comment.
> No, it has to load and deserialize the whole entity (though it only returns a small part of it), since it’s all stored as one JSON blob. Really? This would be a very unfortunate design decision, since it would mean that those entities with larger amounts of data (which tend to be the most interesting ones == the most frequently queried ones) are most inefficient in resource usage. Actually I wonder how query.wikidata.org can be so much faster - https://w.wiki/Dho which queries P373 <https://phabricator.wikimedia.org/P373> for //all 199 countries// is done in a little more than 100 Milliseconds //in total//. So obviously there must be some way to access that property without loading and parsing the whole JSON blob. TASK DETAIL https://phabricator.wikimedia.org/T237884 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Reinhard_Mueller Cc: Lucas_Werkmeister_WMDE, Aklapper, Reinhard_Mueller, Liuxinyu970226, darthmon_wmde, DannyS712, Nandana, Lahi, Gq86, Darkminds3113, GoranSMilovanovic, QZanden, LawExplorer, Vali.matei, _jensen, rosalieper, Scott_WUaS, Jonas, Volker_E, Wikidata-bugs, aude, GWicke, Dinoguy1000, Lydia_Pintscher, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
